Skip to content

Box Setup: Connect & Transfer Files

Box is a cloud storage and file sharing service. In Blober you browse your Box by navigating the folder tree. Box doesn't let you type paths, so you pick a folder or the whole account as a source or destination.

What you can do

  • ✅ Browse folders and files
  • ✅ Upload and download files
  • ✅ Create folders
  • ✅ Delete files and folders
  • ✅ Copy and move files within Box

Prerequisites

Authentication

Blober needs three pieces of information: the Client ID and Client Secret from the app you create in the Developer Console, plus the email of the Box account that holds your files. You paste them into Blober and then sign in to Box to grant access.

The fields in Blober:

Field What it is
Client ID A long string that identifies your app
Client Secret A secret string paired with the Client ID
Box account email The email of the Box account that holds your files

The email is used to keep separate Box accounts apart when they share the same app. Enter the same email every time you connect.

Setup steps

  1. Create a Box Developer account (free trial, needed to create the app)
  2. Create a Box app with User (OAuth 2.0) auth
  3. Add the redirect URI
  4. Enable the permissions and copy your credentials
  5. Connect Box in Blober

Required permissions

In the Box app's Application Scopes section, you need both of these:

Checkbox What it does
Read all files and folders stored in Box Lets Blober see and download your files.
Write all files and folders stored in Box Lets Blober create, upload, and change files.

If either is missing, Blober can't connect fully. Enable both, then reconnect.

Setup guide

1. Create a Box Developer account

On a standard free Box account the Developer Console (where apps are created and configured) is read-only, so you can't save any changes there. To create and configure the app you need a free Box Developer account.

  1. Go to developer.box.com and click Get started (or sign up at account.box.com/signup/n/developer)
  2. Enter your name, email address, and a password. Use an email address that isn't registered with Box yet, because the developer account needs its own.
  3. Accept the terms and click Get Started
  4. Confirm your email address to activate the account
  5. Open the Developer Console at app.box.com/developers/console

Box developer signup form showing the Box Developer plan with API access and 10 GB of storage

Developer account vs. a regular Box account

Use a Box Developer signup, not the ordinary free "Box Individual" signup. The two differ on the signup page and in the app afterwards:

Box Developer account Box Individual (free)
Signup plan shown "Box Developer", includes Access to APIs "Box Individual", storage only
API access Yes (OAuth 2.0, JWT, Client Credentials) No usable API / locked console
Location selector No location step May ask to select a location
Left navigation Shows Admin console and Dev console Does not

A regular Box (Box Individual) signup for comparison, with storage only and no API access

Once signed in, expand the left navigation. A developer account shows Admin console and Dev console there; a regular free account does not.

Box left navigation expanded, showing Admin console and Dev console

2. Create a Box app

  1. Open the Box Developer Console
  2. Click New App (top right)
  3. Enter an App Name (e.g., Blober)
  4. Under App Type, choose User. Don't choose Server: Server apps are for service accounts and can't be used with Blober, and you can't change the type later
  5. Click Create

Create a New App dialog with User selected, where users log in with their own Box account

If the form shows a Select Method option, ignore it. It only applies to Server apps. A User app uses OAuth 2.0 automatically.

3. Add the redirect URI

  1. Open your app and click the Configuration tab
  2. Scroll to the OAuth 2.0 Redirect URI section
  3. Click Add Redirect URI and enter exactly: http://localhost:52847/oauth/box/callback
  4. Click Save Changes

OAuth 2.0 Redirect URIs section on the Configuration tab

4. Enable the permissions and copy your credentials

  1. On the Configuration tab, scroll to Application Scopes and leave the default permissions selected. They are already correct for Blober: Read all files and folders stored in Box and Write all files and folders stored in Box are turned on by default.
  2. Click Save Changes.
  3. Click the App Details panel (top right).
  4. Copy the Client ID.
  5. Reveal and copy the Client Secret (see note below).
  6. Keep both somewhere safe until you paste them into Blober.

The Box app Configuration page, showing the Application Scopes and the Client ID and Client Secret in the App Details panel

5. Connect Box in Blober

  1. In Blober, go to Workflows => New Workflow
  2. Select Box as source or destination
  3. Paste your Client ID and Client Secret, and enter the email of the Box account that holds your files
  4. Click Authorize Box Access. A browser window opens
  5. Sign in with the Box account that holds your files and grant access
  6. The browser redirects back to Blober and you're connected

File organization

Blober creates any missing folders when it uploads.

  • Names are case-insensitive but case-preserving (a folder can't contain both Photos and photos)
  • The root of your Box is the top-level "All Files" view, so selecting the entire drive means picking this root

How uploads work

Files of any size your Box plan allows can be transferred to and from Box.

  • Files up to 50 MB upload in one go
  • Files over 50 MB are split into parts and uploaded in sequence
  • Parent folders are created automatically if they don't exist

Deduplication

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

Choosing Overwrite the existing file uploads a new version onto the same file id, so Box keeps its version history and the destination never ends up with two files of that name.

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

Rate limiting

Box applies limits on how many requests you can make per minute. If you hit a limit, a transfer may pause or fail. Wait a moment and try again.

Reconnecting after a while

If Blober hasn't connected to Box for a while, you may be asked to reconnect. Click Authorize Box Access again and sign in. Your files are not affected.

Troubleshooting

"Authentication failed" or 401 errors

  • The connection expired. Disconnect Box in Blober and connect again.

"Box token is invalid or expired - re-authorize"

  • The connection needs refreshing. Re-authorize Box in Blober (this doesn't affect your files).

"Insufficient permission" (403) errors

  • The Box app isn't set up to read/write your files. Follow the setup steps and enable both the Read all files and folders stored in Box and Write all files and folders stored in Box checkboxes, then reconnect.
  • If the error mentions a specific folder, you may not have access to it in Box itself. Check the folder's sharing in Box.

Redirect URI errors (redirect_uri_mismatch / redirect_uri_missing)

If the redirect URI doesn't match, Box shows an Application Error page with Error: redirect_uri_mismatch and you're never redirected back to Blober.

  • Register the exact Redirect URI http://localhost:52847/oauth/box/callback in the app's Configuration tab. It must match exactly: no trailing slash, http (not https), port 52847, and the full path /oauth/box/callback.
  • Click Save Changes after adding it.
  • If you configured multiple redirect URIs, ensure the one Blober uses is among them.

"Some changes in the configuration could not be saved"

Box shows this when one of the fields on the Configuration tab is invalid, so the whole save is rejected. With a redirect URI, the usual causes are:

  • A regular (non-developer) Box account. This is the most common cause: the Developer Console is read-only on standard free accounts. If the console also shows "Log in or sign up for a Box Developer account to access all of the Developer Console features," you need a free Box Developer account at account.box.com/signup/developer. Create the app there, and the redirect URI and scopes will save.
  • A trailing slash on the URI. Enter it exactly as http://localhost:52847/oauth/box/callback, with no trailing /.
  • A stray space or character. Type the URI instead of pasting it from a source that may add invisible characters.
  • A duplicate URI. If it's already in the list, remove the duplicate.
  • Another invalid field on the same page. Add only the redirect URI (leave scopes and CORS unchanged) and save, then add the scopes and save again. If an empty or malformed CORS entry is the problem, clear it.

Missing credentials

  • Ensure both Client ID and Client Secret are filled in, with no leading/trailing whitespace.

Files not appearing

  • Refresh the file list in Blober.
  • If the file was deleted to Box Trash, it won't appear in normal browsing.

How to revoke access

  1. Go to your Box account settings and find Authorized Applications
  2. Remove the Blober app
  3. In Blober, remove the existing connection

Revoking access invalidates all tokens immediately.

Limitations

  • No path-based navigation. You pick a folder (or the whole Box) instead of typing a path.
  • No separate "Shared with me" view. Folders shared with you appear inside your normal file list (see File organization).
  • Deletes go to the Box Trash. Deleted items still count toward your quota until the Trash is emptied.
  • Filename rules. Names can be up to 255 characters, can't contain \ / < > : " | ? * or leading/trailing spaces, and are case-insensitive (so Photo and photo can't both exist).

Further reading