pCloud Setup: Connect & Transfer Files

pCloud is a cloud storage service with US and EU data centers. In Blober you browse your pCloud by navigating the folder tree. pCloud doesn't support path-based access, so you pick a folder or the whole account as a source or destination.

• ✅ Browse folders and files
• ✅ Upload files
• ✅ Download files
• ✅ Create folders (created automatically when uploading)
• ✅ Delete files and folders (folders recursively)
• ✅ Copy files within pCloud
• ✅ Move files within pCloud

• A pCloud account (free or paid)
• No pCloud app needed to get started. The App Key and App Secret are pre-filled with Blober's registered pCloud app, so you can authorize right away. Prefer your own app? See Create a pCloud App.

Blober connects to pCloud using your app's App Key and App Secret via the OAuth 2.0 authorization-code flow.

Credential fields:

Field	Description	Default
App Key	Your pCloud app key (short alphanumeric string)	c07tF0mXr10
App Secret	The secret paired with your app key	NjSmWPr0IuJDzmIDXdLGijP6gTDV

The App Key and App Secret fields are pre-filled with the credentials of a pCloud app registered by Blober (shown as Blober - Cloud File Migration during authorization). This is the fastest option - you authorize in seconds with no app setup or review wait.

Prefer the open-source rclone app instead? Its public keys are still supported - replace the pre-filled values with:

Credential	Value
App Key	DnONSzyJXpm
App Secret	RUqH9GooHqkC4IFkifsD1haRu9fy

These are rclone's real public keys, verifiable in its pCloud backend source (rcloneClientID and the obfuscated rcloneEncryptedClientSecret).

With the pre-filled keys you can skip app creation entirely:

1. In Blober, go to Workflows => New Workflow
2. Select pCloud as source or destination
3. Keep the pre-filled App Key and App Secret, or paste rclone's keys from above
4. Click Authorize pCloud Access - a browser window opens for consent
5. Sign in with your pCloud account and grant permissions
6. The browser redirects back to Blober automatically and you're connected

Only needed if you prefer not to use Blober's pre-filled keys (rclone's public keys from the table above are another no-setup alternative).

1. Sign in to the pCloud App Console and select Create app (or New app)
2. Fill in the app details as below
3. Save the app
4. Copy the Client ID and Client secret it generates - these become your App Key and App Secret in Blober

The console asks for a few details. Values that work for connecting Blober:

Field	Suggestion
App name	Blober - Cloud File Migration (any name you'll recognize)
Publisher	Blober (or the name you publish under)
Description	Desktop app that transfers files between pCloud and other cloud or local storage.
Redirect URIs	http://localhost:52847/oauth/pcloud/callback
Website	https://blober.io
Allow implicit grant	Disallow - Blober uses the authorization-code flow only

App icon (optional): must be 64 x 64 px. Use Blober's logo if you want it to match the brand.

Blober's callback runs on that exact local address, so your app must allow it: http://localhost:52847/oauth/pcloud/callback

The Redirect URIs field accepts http://localhost addresses. Blober's own app and rclone's app already register the callback Blober uses, so this step applies only to apps you create yourself.

pCloud runs two data centers: US (api.pcloud.com) and EU (eapi.pcloud.com). The authorization redirect identifies the account's data center.

pCloud has no path-based API. Blober resolves paths by walking the folder tree from the root (folderid 0) and matching folder names, creating missing folders automatically when uploading.

• Names are case-sensitive (unlike Box or Google Drive), so Photos and photos are different folders
• A file and a folder may share the same name in one folder
• Folders are created automatically when uploading to a path that doesn't exist yet

• Files are uploaded to pCloud in a single request. Account, server, and connection limits apply - pCloud publishes no universal maximum file size.
• Parent folders are created automatically if they don't exist.

• Default: Skip if a file with the same name exists
• Used for: Destination

For the policies (skip, overwrite), where the control appears, and how deduplication differs from resuming a task, see Deduplication.

pCloud documents no scheduled expiry for access tokens. A token can still become invalid when access is revoked or pCloud rejects the login.

pCloud classifies 4xxx results as rate limiting and 5xxx results as temporary server failures. Blober retries these automatically.

• The app was revoked from your pCloud account settings. Remove the connection in Blober and authorize again.

• Ensure the App Key and App Secret belong to the same app and are entered correctly, with no leading/trailing whitespace.

• Refresh the file list in Blober.
• Check the files exist in your pCloud account (in the correct data center region).

• If an upload fails, start it again - Blober retries the file from the beginning. Your existing file at the destination is not lost.

1. Go to your pCloud account settings and find Linked Accounts
2. Remove the Blober app
3. In Blober, remove the existing connection

Revoking access invalidates the token immediately.

• No path-based API: Blober walks the folder tree, so paths resolve by folder name.
• No resumable uploads: each file uploads in a single request; a failure retries the whole file.
• Case-sensitive names: migrating from a case-insensitive provider may create duplicate-looking folders.
• Filename rules: UTF-8 names up to 1024 bytes; only /, \, and NULL are forbidden.