Clio storage & file size limits
Where do files actually live in Clio, how do you reach them from your desktop, what counts toward storage, and how big can a single upload be? These are the practical questions that come up the moment a firm moves real document volume into Clio. This guide answers them and covers the three ways to access Clio files — the web Documents area, Clio Drive, and keeping some files in external storage — with the trade-offs of each.
Where your files live, and how much fits
One storage system, three front doors
Files in Clio live in one place — attached to a matter (or in the firm-wide document space) — but you reach them three ways, and picking the right one for a given task is most of what "file management" means day to day. The web Documents area is the browser interface: best for browsing a matter, sharing to the client portal, and bulk actions. Clio Drive is a desktop app that mounts Clio storage like a network drive, so files behave like local files inside Word or your file explorer: best for heads-down editing. And some files reasonably stay in external storage entirely.
The sections below cover each, plus the two practical limits people hit — storage volume and single-file size — and how version history interacts with both. For the desktop option specifically, the dedicated Clio Drive guide covers the streaming sync model, setup, and troubleshooting in depth.
Documents area, Clio Drive, or external
| Access path | Best for | Watch out for |
|---|---|---|
| Web Documents area | Browsing matters, sharing to the client portal, bulk upload and moves, full-text search | Editing round-trips (download, edit, re-upload) are slower than native; full-text search runs through Clio's global search bar and is a higher-tier plan feature |
| Clio Drive (desktop) | Daily editing in Word/Excel; files behave like local files; background bulk copies | Requires install + sign-in per machine (not on the North America Starter plan); sync state to be aware of |
| External storage | Co-authored working drafts, firm-wide operational files, very large media | Version drift — the matter copy goes stale if you forget to file the final |
Most firms use the first two together — the web area to organize and share, Clio Drive for the editing day — and reserve external storage for files that genuinely don't belong in a matter. The danger with external storage is version drift: a draft edited in a cloud folder and never re-filed leaves the matter holding a stale copy. The clean pattern is "draft externally, file the final into Clio," so the matter always holds the canonical version. Clio can also natively connect Dropbox, Box, Google Drive, and OneDrive for Business as document sources, so files kept in those services surface in the matter's Documents area (confirm current setup details in Clio's help center). Getting that final version in from a cloud source like OneDrive or SharePoint is its own workflow, covered in the OneDrive & SharePoint guide (or, when that connection is the thing failing, its troubleshooting sibling); for firms whose files live in Dropbox, the Dropbox guide covers the same move.
How much can you store?
For ordinary matter documents — pleadings, correspondence, contracts, scanned exhibits — storage volume is rarely the constraint on Clio's paid plans, which market unlimited document storage. There's no formal per-firm cap; Clio only flags accounts whose usage runs into the hundreds or thousands of gigabytes, which normal document work never approaches. For everything firms file day to day, you can store freely.
Where size actually warrants attention is large media: multi-hour continuous video recordings, large native datasets from e-discovery. For those the constraint is usually the 5 GB per-file limit (covered next), not your total storage — so the decision is per file: does this one live in the matter, in external storage referenced from the matter, or both. When that per-file question becomes a firm-wide one — which venue client documents should sit in at all, and what custody obligates once they do — the legal document storage guide covers the four realistic options. For ordinary documents, the cost of a missing file dwarfs the cost of the bytes.
The two limits that actually bite — 5 GB per file, and versions
Per-file size. Clio caps a single file at 5 GB, and that ceiling is the same through the web Documents area and through the Clio Drive desktop app — switching to Clio Drive does not let a larger file through. A file over 5 GB has to be split into smaller files or kept in external storage and referenced from the matter; no upload method beats the cap, and zipping only helps when the contents compress (video, audio, and PDFs barely do). Most files clear 5 GB easily, so this only matters for outsized ones — a multi-hour continuous video, a large native production — and the fix is to split them or store them externally before you start, rather than hitting the cap mid-upload. If a file well under 5 GB still won't upload, the size limit isn't what's stopping it: see what to do when a Clio upload isn't working.
Versions and storage. Version history keeps prior versions of a document rather than overwriting, which is exactly what you want for a draft that goes through rounds. For typical office documents the storage footprint of old versions is negligible against the value of keeping earlier versions available — and note that there's no one-click revert in the web interface: to make an older version current, you add it back as a new version (the "+" icon next to Version history). The exception is large binary files versioned repeatedly — every version of a 200 MB file is another 200 MB. For those, version the small source document and store large renders separately rather than re-uploading the whole large file as a new version each time.
Both limits are easy to live with once you know them: effectively unlimited storage for ordinary documents, 5 GB for any single file. The cost of ignoring the per-file cap is always paid at the worst time — mid-upload, on a deadline — so when a transfer involves an outsized file, plan to split it or store it externally before you start.
Moving real volume in
When you're loading an existing file set — onboarding a firm to Clio, migrating a matter, or filing a big production — the efficient paths are drag-and-drop of multiple files and folders into the Documents area, copying via Clio Drive, or a bulk-upload tool for high volume. The slow path is the one-file-at-a-time web picker.
Whatever the method, decide the folder template and naming convention before you start. Moving files in fast and organizing later almost always means the organizing never happens — you've just recreated the desktop mess inside Clio. The folder structure and naming guides cover the templates worth setting up first.
For recurring inbound files — court filings, signed agreements, email attachments — the question shifts from "how do I bulk-load" to "how do I make each file land in the right matter with minimal friction," which is where official integrations, Power Automate flows, and browser tools like Send to Case each have a place. The comparison of tools for uploading to Clio weighs them honestly.
How much document storage does Clio include?
+Clio markets unlimited document storage on its paid plans, and there's no formal per-firm cap — Clio only reaches out about accounts whose usage runs into the hundreds or thousands of gigabytes, which ordinary document work never approaches. So for matter documents — pleadings, correspondence, contracts, scanned exhibits — storage volume is simply not the constraint. The limit you'll actually meet first is the per-file ceiling: a single file can be up to 5 GB. Very large media (hours of video, large native datasets) is where that 5 GB per-file cap, not total storage, becomes the thing to plan around.
Is there a file-size limit for a single upload?
+Yes — Clio's limit for a single file is 5 GB, and it's the same whether you upload through the web Documents area or copy the file in through the Clio Drive desktop app. Switching to Clio Drive does not raise the ceiling: Clio publishes the 5 GB per-file limit for both. A file larger than 5 GB has to be split into smaller files or kept in external storage and referenced from the matter — no upload method beats the cap, and zipping only helps when the contents compress (video, audio, and PDFs barely do). Most individual files clear 5 GB comfortably; where it matters is the occasional outsized file, like a multi-hour continuous video recording or a large native production, so check those against the 5 GB limit before you start rather than discovering it mid-upload.
Can you upload a ZIP file to Clio?
+Yes, but Clio doesn't unpack it. When you upload a .zip file to a matter in Clio's web Documents area, it's stored as a single file, so the documents inside don't appear individually in the matter. If those files need to live in the matter on their own, unzip the archive on your computer and upload the contents, or use an upload tool that extracts the archive into the matter for you.
What is Clio Drive and how is it different from the Documents area?
+Clio Drive is a desktop application that mounts your Clio documents like a network drive in your operating system's file explorer, so you can open, edit, and save matter files directly from Word, Excel, or Finder/Explorer without a browser round-trip. The Documents area is the web interface to the same files. They're two front doors to one storage system: the Documents area is best for browsing, sharing, and bulk actions; Clio Drive is best for heads-down editing where you want files to behave like local files. Many firms use both — the web area for organizing and the Drive for daily editing. Clio Drive is included at no extra cost on every Clio Manage plan except the North America Starter plan.
Do old versions of a document count toward storage?
+Version history retains prior versions of a document, so logically those bytes are stored somewhere. For typical office documents the footprint is small enough that it doesn't matter in practice, and the value of keeping earlier drafts available outweighs the storage — note that there's no one-click revert in the web interface; to make an older version current, you add it back as a new version. Where it can add up is large binary files versioned repeatedly — each version of a 200 MB file is its own 200 MB. For those, prefer versioning the small source document and storing large renders separately, rather than re-uploading the whole large file as a new version each time.
Should every file go into Clio, or keep some in external storage?
+Client matter documents belong in Clio — it's the system of record and what makes them findable and auditable. The files that reasonably stay external are firm-wide operational documents (HR, internal templates being actively co-authored, knowledge base content) and very large media that doesn't need to live in the matter day to day. A common pattern is to keep working drafts in a cloud-storage collaboration space and file the final version into Clio, so the matter holds the canonical document while the messy drafting history stays out of it. The rule of thumb: if it's evidence of or work product on the matter, it goes in Clio.
What happens to files when a matter is closed?
+Closing a matter in Clio doesn't delete its documents — they remain stored and accessible, just on a matter marked closed, which keeps your active matter list clean while preserving the file. This is the right behavior for legal records: retention obligations usually run for years after a matter ends. If you need the documents outside Clio (for archival, for handing a file to a client, or for a records-retention process), Clio supports exporting documents. How long to keep closed-matter files and how to dispose of them afterward is a retention-policy question covered in the retention guide.
How do I move a large batch of existing files into Clio efficiently?
+For a one-time load of an existing file set, the efficient paths are drag-and-drop of multiple files or folders into a matter's Documents area, the Clio Drive desktop app (copy files in as you would to any drive), or a bulk-upload tool for high volume. The slow path is uploading one file at a time through the web picker. Whichever method, decide the folder structure and naming convention first — moving files in fast and organizing later usually means the organizing never happens, and you've recreated the desktop mess inside Clio.
Keep going
Clio document management guide
The full picture: folders, naming, versions, permissions, search, and retention.
Read guide →Clio folder structure
Default folder sets and matter templates so files land somewhere sensible.
Read guide →Document retention & records
What happens to files long-term and how to build a retention schedule.
Read guide →Clio document permissions
Who can see which files across the three access surfaces, and how to govern it.
Read guide →Skip the download-and-reupload step
A free Chrome extension: right-click a Gmail attachment or a download link on a court or client portal, and file it straight to the right Clio matter.
10 uploads a month free. No credit card required. See pricing