Box
Files.com can connect to Box as a remote server using a Remote Server Mount or a Sync. It can be used to exchange files with a counterparty's Box, and to connect with an internal Box that your own business processes depend on.
A company whose partner delivers files through Box can mount that folder into Files.com and process them alongside every other counterparty, with no change on the partner's side. A team whose internal processes are built around Box can connect to it and work through Files.com without disrupting those processes.
Some customers also use the integration to migrate off Box. A scheduled pull Sync moves documents into Files.com in batches while internal teams keep working in Box until cutover.
Box is designed for content management and team collaboration. For storing data long-term, native Files.com storage or dedicated cloud storage (S3, Azure Blob, Google Cloud Storage) is more dependable, so use the Box integration when the data genuinely needs to stay in Box, not as a default storage backend.
Working with Box
Box has limitations when handling large amounts of data or large numbers of concurrent file transfers. Files.com has built additional features to improve connectivity.
Box rate-limits its inbound traffic APIs, so it ingests data more slowly than users can upload it. To handle this, Files.com automatically enables Buffered Uploads for Box remote servers. Users upload to Files.com at full speed, and Files.com forwards each file to Box in the background at whatever rate Box accepts.
Box performance depends on folder size: large folders slow listings, sync, and API responsiveness, so keeping folders within the recommended range keeps the connection responsive.
Box uses OAuth for authentication, so the connection needs periodic re-authentication. When re-authentication is needed, Files.com records the event in the External Events log and shows an alert in the web interface. Following that alert re-establishes the connection right away. Box's default re-authentication period is 60 days.
Case Sensitivity
Box is case insensitive. When files or folders whose names differ only in capitalization are transferred between Box and a case-sensitive system, Box treats them as the same item and resolves the conflict by renaming the incoming file, for example appending _2 to the name. A consistent naming convention across both systems is the reliable way to avoid this.
Add Box as a Remote Server
Create a new Remote Server for your site, and select Box as the remote server type.
You must provide an Internal name for this connection. If you're managing multiple remote servers, make the name clear enough to easily identify this particular connection.
The options for specifying Dedicated IPs and Data Regional Routing will only appear if your site is configured to allow those options. Dedicated IPs are only available when a Custom Domain has been configured. Data Regional Routing is only available if your top-level, or root, folder is set to a non-USA geographic region.
Once your new Remote Server is saved, complete the authentication and authorization with Box. A popup displays the Box login form. Logging in connects your Files.com site with your Box account.
After your Remote Server is connected, you can use it with Files.com as either a Remote Server Mount or Sync.
Box Authentication and Authorization
Make sure the permissions of the Box user account are correct. Files.com can only perform actions allowed for the Box user. Authenticate using a Box user account that has "Editor" permissions or higher.
Box uses OAuth for authentication, so the connection needs periodic re-authentication. Authentication errors can occur even after a remote server has been configured and running smoothly for some time. When re-authentication is needed, Files.com records the event in the External Events log and shows an alert in the web interface. Following that alert re-establishes the connection right away. Even without changes to the configuration, saving the remote server record causes Files.com to re-enable the connection. Any associated mounts and syncs resume working.
Using Multiple Box Accounts
You can create as many Box Remote Servers as required. Repeat the above instructions and enter different credentials each time the Box login page is presented.
If you are using Single Sign-On (SSO) with Box, your web browser always tries to log you in using your currently logged-in credentials. The popup Box login page automatically logs you in without giving you the option to enter different credentials. This is normal web SSO behavior.
To connect a different account, use the Reset Authentication option on the Remote Server. This clears the stored Box credentials so you can authenticate again as the account you want. If your browser still logs you in automatically as the wrong account, log out of Box in your web browser before re-authenticating, use an incognito window, or use a computer and browser that has not logged into Box yet.
Add Remote Server Mount
A Remote Server Mount connects a folder on Files.com to the Box remote server in real time. Any operation you perform in that folder passes through to Box as it happens.
Mounts are created by mounting them onto an empty folder in Files.com. We recommend that this folder not be the Root of your site, although the Root is supported if you need it.
Add Sync
A Sync copies files to or from Box. A sync can push files from your Files.com site to Box, or pull files from Box to your Files.com site.
Automations
Folders configured with a Remote Server Mount to Box can be used with automations as source locations or destinations.
Folder Size Recommendations for Box
Box has lower performance characteristics than many other storage platforms, particularly for folders containing large numbers of items. Folder size has a direct impact on reliability, sync performance, listing speed, and API responsiveness. Our analysis shows that Box's performance begins to decline at lower folder sizes than most other remote providers.
Box performs best when folders remain relatively small. Folders containing 250 to 500 items offer the most stable experience. Within this range, folder listings, sync operations, and API-driven workflows run consistently.
Folders that grow to around 1,000 items still function acceptably, but listings become noticeably slower and sync cycles run longer. This size represents the upper end of what is practical when integrating with Box.
Once a folder exceeds 1,000 items, performance degradation becomes likely. Browsing and syncing experience delays or intermittent timeouts. We recommend maintaining folders well below this threshold.