Connect Box when a partner delivers documents there or an internal team needs to keep its working content in Box. Files.com adds its own access methods and file workflows around that content. A Mount exposes the Box files themselves; a Sync transfers a separate copy, including for a migration while the original service remains in use.

Use this integration for content that needs to participate in Box's collaboration model. For a new storage location behind a file-transfer workflow, we recommend Files.com Native Storage or dedicated cloud storage rather than Box. Box's request limits and folder sizes affect how quickly Files.com can list and transfer its files.

Account Access

Select Box when adding a Remote Server. Box uses OAuth: authorize the connection with the Box account that should supply access to its files. The account's Box permissions govern remote operations. An Editor account supports file management; a narrower account must still have the permissions needed for the intended reads, uploads, replacements, or deletions.

Files.com folder permissions separately govern who can use a mounted Box folder. Giving a Files.com user write access does not grant the connection write permission in Box.

Box distinguishes previewing a document from downloading its original contents. Watermarking can allow a Viewer to preview a file while preventing the original-file download Files.com needs. Confirm the account's Box permissions and the file's download restrictions when investigating a download failure.

Multiple Box Accounts

Create a separate Remote Server for each Box account. The browser may reuse its existing Box or SSO session during authorization. To change the connected account, use Reset Authentication; if the provider selects the wrong account automatically, sign out of Box or use a private browser session before authorizing again.

Files.com renews access tokens automatically while the authorization remains valid. Follow Re-authenticating Remote Servers when the provider requires a new sign-in, rather than treating each token expiry as a reason to reconnect manually.

Upload Delivery

With Buffered Uploads set to Automatic, Files.com stages Box uploads before forwarding them at the rate Box accepts. The client can finish without remaining connected for that delivery stage. Upload completion then confirms receipt by Files.com, rather than availability in Box. Buffered Uploads explains delivery results, retries, and the temporary copy.

Box also applies API rate limits. Buffering helps separate incoming upload speed from delivery speed; it does not remove Box's limits on uploads, listings, or other requests.

Folder Size Recommendations for Box

Keep Box folders small for workflows that repeatedly list or sync their contents. We recommend approximately 250 to 500 items per folder for the most stable experience and keeping folders well below 1,000 items. Larger folders take longer to list and can produce longer Sync runs, delays, or timeouts.

These are operating recommendations, rather than Box's maximum folder capacity. Organize deliveries into folders that the workflow can process independently, and assess performance with the actual file counts and workload.

Case Sensitivity

Box uses case-insensitive names. Names differing only in capitalization cannot serve as distinct destinations in the same folder. Resolve those collisions before copying or syncing from a case-sensitive source, rather than relying on a rename to preserve the intended relationship between files.