Create Accountor Login
Docs

Uploading Many Files

Part of the MountDev Ops Files documentation. Updated November 20, 2026

MountDev Ops Files documentation | Updated November 20, 2026

Every upload in your workspace goes through one queue and one tray: files in a folder, the Files card on any record, meeting recordings, files you share from a Helpdesk ticket, and pictures for a website. You can choose many files at once, keep working while they go up, and move around the workspace without losing them.

The Upload Tray

The tray sits at the bottom left of the page, beside the menu and never over the Chat button. On a phone it is a bar across the bottom, with the corner of the Chat button left free. It is not a pop up: nothing is blocked, and you can keep using any screen. It appears when you add the first file, stays while anything is unfinished, and fades away a few seconds after everything has finished with nothing failed.

Collapsed, the tray is one bar. It says "Uploading 12 of 28", and ", 2 failed" or ", 1 cancelled" when those are above zero. Under the words is one bar for everything, counted by bytes, which reaches the end only when the last file is stored. Pause stops and starts the whole queue, and the arrow opens the list.

Open, the tray adds Cancel All, Retry Failed (only when something failed), and the list. The list shows only files that are not finished, up to six at a time, then scrolls inside the tray:

  • Uploading, with its own bar and percent.
  • Waiting, for its turn.
  • Paused, while the queue is paused.
  • Waiting for your connection, while your connection is down (see below).
  • Waiting to try again, when the server asks for a short wait.
  • Failed, with the reason in a sentence, and Retry and Remove.

A finished file fades out of the list and is only a number in the summary. When everything is done the tray says "28 of 28 uploaded". In a Files folder it also offers Open Folder, and Close.

Collapsing the tray, or moving to another page, another app, or Settings, never changes an upload. The tray is the same one wherever you go.

How Files Go Up

  • Three files at a time. A fourth starts when one finishes. Files start in the order you chose them.
  • One piece after another inside a file. A big file goes up 5 MB at a time, in order, and the server keeps each piece as it arrives.
  • Pause and Resume. The piece already on its way finishes, then nothing new starts until you select Resume. Nothing is lost.
  • Cancel on a file stops it and removes its pieces from storage. Cancel All asks first ("Stop 16 uploads? The 12 already uploaded stay.") and leaves every file that is already stored.
  • Retry Failed puts every failed file back in the queue. A file that had already sent some pieces carries on from the next one.

When Your Connection Drops

A file whose piece cannot be sent shows Waiting for your connection, and the queue tries again after 2, 4, and 8 seconds, then every 30 seconds, and at once when your browser says it is back online. Each try asks the server how many pieces it already has and sends from the next one, so nothing already sent is sent again. A piece the server already holds counts as sent, and if the server has forgotten an upload (one left open more than a day), the file is started again once.

After 10 minutes with no connection the file is marked Failed with a reason, and Retry carries on from where it stopped. When the server answers that it is busy, with a wait, the file waits that long and tries again.

If your sign in ends, the whole queue pauses and the tray says "Your sign in ended. Sign in again, then press Resume." If signing in does not reload the page, Resume carries on. If it does, the files that were not sent are gone, the same as when a tab is closed.

Choosing Files or a Folder

In a folder, Upload is one button with two choices:

  • Files chooses one file or many.
  • Folder chooses a whole folder. It is not shown where your browser cannot choose a folder, which is most phones. There the button is Upload Files.

You can also drop files, or a whole folder, onto the folder's Files list. While you drag, the list says "Drop to upload to" and the folder's name.

Whole Folders Keep Their Shape

A folder you choose or drop keeps its structure. The folder's name becomes a folder inside the one that is open, with its subfolders and files. Empty folders come over too.

  • A folder with the same name is merged into. If Spring Photos is already in the open folder, the files go into it and the folder is not made twice. Names are compared without regard to capital letters, and an accented name written the way a Mac writes it is the same as the same name written any other way. A file with the same name as one already there is handled as any other upload.
  • The pop up says what will be made before anything is sent: "Makes 4 folders." or "Spring Photos is already here, so its files go into it." Nothing is made until you select Upload, and Cancel makes nothing.
  • The folders are made first, in one step, the same way New Folder makes one, so each is an ordinary folder with its history. A folder made inside a private folder is private with it. Then every file goes into its own folder through the same tray.
  • Open Folder in the tray opens the folder you dropped onto.
  • Computer files are skipped and counted, never listed one by one: .DS_Store, Thumbs.db, desktop.ini, files that start with ~$ or ._, and the other files a computer keeps for itself (the ones the Network Drive also keeps out of Files). The pop up says "3 computer files were skipped."

The Limits for One Drop

One drop or choice can hold up to 2,000 files, 500 folders, and 8 levels of folders. Past that, nothing starts and a message says so in plain words with the one next step, for example: "That is more than 2,000 files. For a big move, set up the Network Drive and drag and drop your folders there, with no limit. Select Set Up the Network Drive." The button opens Account, Network Drive, where you set up your computer; folders you drag there keep their structure and have no limit. If your company does not let you use the Network Drive, the message leaves that part out and says to upload a smaller part now and drop the rest after these finish.

Checks Before Sending

Each file is checked in your browser before anything is sent, and the server checks again with the same words (the Network Drive is the one way an empty file is made, because Finder and File Explorer make one first). A file that fails is left out, told in plain words, and the rest go up:

  • Over 10 GB: "movie-raw.mov is 12 GB. Files can be up to 10 GB."
  • Nothing in it: "notes.txt is empty, so there is nothing to upload."
  • Not a picture (the Pictures page of a website only): "price-sheet.pdf is not a picture. Pictures here are PNG, JPEG, WebP, or GIF."

Where several files are chosen at once, the folder's pop up lists them under Cannot Be Uploaded. Anywhere else, the tray lists them until you select Dismiss. Files itself takes any kind of file: there are no new kinds refused when you upload to a folder.

Who Can Load This

The choice you make for a batch (Private or Public, see Who Can Load a File) is part of each file's own entry in the queue, and it is saved as you chose it. After a file is stored, the tray asks for Public for it and reads the answer. A file that could not be made Public stays Private, and the tray lists it with the reason ("report.png was uploaded and is Private: Public files are turned off for your company.") until you select Dismiss. It never fades by itself. Private is always the start choice.

Leaving While Uploads Are Going

  • Moving inside the workspace does nothing to your uploads.
  • Sign Out and Switch Company ask first while uploads are going: "Uploads are still going. If you leave now, 4 files will not be uploaded." Stay is the first choice, and Leave Anyway is the other.
  • Closing or reloading the tab shows your browser's own "Leave site?" warning. Its words are the browser's and cannot be changed. The warning is on only while something is unfinished, and is removed the moment everything is done.
  • Closing the tab stops unfinished uploads. The tray says so while it is working. Files that were whole stay. A half sent file is cleared by the server within a day. To upload it, choose the file again.
  • A newer version of MountDev Ops never loads in the middle of an upload. It waits until the uploads are done.

Keyboard and Screen Readers

The tray is a labeled region called Uploads. Every control is a button with a name, such as "Pause uploads", "Cancel all uploads", "Retry 2 failed uploads", and "Cancel report-march.pdf". Tab reaches the tray after the page's main content, and Esc collapses it when you are in it. A polite announcement says the summary at most every 5 seconds and when all uploads finish, and a failure is announced once. A bar is labeled with its file and percent and is not announced on every change. Every state has a word, never color alone.

For Developers

The tray is for people. Two new actions serve it, both for signed in people only. core.files.folders.ensure makes the folders a dropped or chosen folder needs, inside one folder you may add to: each path is made when it is missing, a folder already there (found without regard to capital letters or how an accent is written) is used, and a second call makes nothing. It makes ordinary folders the same way New Folder does, so history and private folder rules come with them, and it refuses a folder you cannot add to as one that does not exist when you cannot see it. It allows up to 500 folders and 8 levels. core.files.upload.status answers what the server holds of one of your own uploads (how many pieces have arrived, and the file when it is finished), so the tray can carry on after a drop. It is for signed in people only: an AI agent or an API key cannot use it, nobody can ask about another person's upload, and another company's uploads never show. It changes nothing. Neither action is available to an AI agent or an API key; an agent adds folders one at a time, as it adds any record. The upload actions you may already use (core.files.upload.start, the pieces, and core.files.upload.cancel) are unchanged. The queue lives in your browser tab's memory only: no file name, size, or path is kept by the page.

Ask Us Anything

We’d love to hear from you!