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.

Intended Capabilities

• ✅ 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

Prerequisites

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

Authentication

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)	DnONSzyJXpm
App Secret	The secret paired with your app key	RUqH9GooHqkC4IFkifsD1haRu9fy

Default: rclone's public app keys

The App Key and App Secret fields are pre-filled with the public credentials of a pCloud app registered by the rclone project, a widely used open-source file-transfer tool.

We default to these keys because pCloud reviews every app manually before approval, and there is no sandbox or test environment to develop against. Requiring an app review just to run a file transfer would be unreasonable.

You can confirm these are rclone's real public keys in the rclone source: the pCloud backend defines rcloneClientID and the obfuscated rcloneEncryptedClientSecret.

We are registering blober.io with pCloud. Once the review passes, our own keys will become the default.

Setup steps

With the pre-filled rclone 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 your own
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

Note

With rclone's pre-filled keys, no redirect URI needs to be registered on pCloud's side - Blober handles the local callback itself. If you use your own pCloud app instead, add the redirect URI shown in Create a pCloud App.

Setup Guide

1. Create a pCloud App

1. Go to the pCloud App Console and sign in
2. Select Create app (or New app)
3. Name the app something you'll recognize, for example Blober App
4. Fill in the app details as below
5. Create the app
6. Copy the App Key and App Secret it generates

The form asks for a few details. A setup that works for connecting your own account:

Field	Suggestion
App name	Blober App (any name you'll recognize)
Application Type	Personal use
Folder access	All folders
Write access	Yes
Website	Optional - can be left blank
Expected # of users	A small number, e.g. 1
Reason	Briefly say you're connecting a file-transfer tool

Add the redirect URI (only for your own app)

In the pCloud App Console, open your app's OAuth settings and add this exact Redirect URI:

http://localhost:52847/oauth/pcloud/callback

Blober's callback runs on that local address, so your app must allow it. With rclone's pre-filled keys this step is not needed.

App review

pCloud reviews apps created in My Apps to check security and compliance, so your new app may show as Pending review before it is approved. This does not block connecting it in Blober. While a review is pending, you can also generate a static access token from the pCloud App Console to run personal scripts and private tools directly, without waiting for the review. See the pCloud developer documentation for how to generate one.

Data Centers

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

File Organization

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

How Uploads Work

• Files are uploaded to pCloud in a single request. Account, server, and connection limits apply - pCloud publishes no universal maximum file size.
• Overwrite-first: if a file already exists at the destination, it is replaced with the new version.
• Parent folders are created automatically if they don't exist.

Access Tokens Never Expire

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

Access is revocable only from your pCloud account settings. If you ever see a "Log in failed" error, the app was revoked - remove the connection in Blober and authorize again.

Rate Limiting

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

Troubleshooting

"Log in failed" errors

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

Authentication failed / Permission denied

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

Files not appearing

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

Uploads failing mid-way

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

How to revoke access

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.

Limitations

• 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.

Terms Compliance

Your use of pCloud through Blober is subject to pCloud's Terms of Service. See our Terms of Service for details.