# NetDocuments File Size Limits, Upload Caps, and Large File Storage

The NetDocuments file size limit restricts standard web uploads to 2 GB while supporting files up to 50 GB through list-view drag-and-drop and ndOffice. However, files exceeding the threshold lose search indexing, OCR processing, and DLP tagging, creating friction for litigation teams handling video evidence and discovery archives. Law firms pair their document repositories with external workspaces to store, review, and exchange multi-gigabyte records.

Source: https://fast.io/resources/netdocuments-file-size-limit/
Author: [Derek Labian](https://fast.io/authors/derek-labian/)
Last reviewed: 2026-09-27

## What Are the NetDocuments File Size Limits Across Web and ndOffice?

As of September 2026, the NetDocuments file size limit restricts document uploads to 2 GB across most web destinations while supporting files up to 50 GB exclusively through list-view drag-and-drop or ndOffice. For legal operations leads and law firm IT directors, managing document caps is not an abstract storage exercise. It directly dictates whether trial teams can store high-definition deposition recordings, electronic discovery load files, computer forensic images, and exhibit bundles inside their core matter files.

Historically, NetDocuments operated under tighter document thresholds, enforcing a strict one-gigabyte ceiling for PDF records and capping SetBuilder binder operations at two gigabytes. While NetDocuments expanded its architecture, that expansion comes with rigid operational boundaries. The larger threshold is not available universally across the web application. When a paralegal or litigation attorney attempts to upload a large file through standard folder menus, web forms, or older add-ins, the upload fails immediately with an error message stating that the file exceeds the file size limit in the selected destination.

To achieve an upload up to the 50 GB ceiling, users must satisfy three technical conditions:

* **Supported Upload Pathway:** Documents up to 50 GB can be uploaded to the NetDocuments platform using the drag-and-drop feature (in the list view of a filter or folder) or via the ndOffice add-in.

* **Repository Configuration:** A repository administrator must enable the repository setting permitting large files located within the NetDocuments Admin Console under Information and Settings.

* **Encryption Architecture Compatibility:** The 50GB upload capability is currently unavailable for FlexStore and CMEK users. For organizations operating under Customer Managed Encryption Keys (CMEK) or FlexStore, the repository setting is automatically disabled and greyed out.

Even when these criteria are met, desktop stability remains a persistent bottleneck. Browser sessions uploading multi-gigabyte files require constant network stability. If an attorney switches networks, closes their laptop lid, or experiences transient latency during an upload via ndOffice or the web interface, the session terminates. Because native web uploads do not feature automated background pause-and-resume mechanisms, staff must restart the transfer from the beginning, consuming billable hours and delaying court filing deadlines.

## Why Files Exceeding the Threshold Lose Search Indexing and Governance

The primary challenge for law firms is not merely getting large files into NetDocuments, but what happens to those records once stored. In legal document management software, an unindexed document is an operational liability. Trial lawyers and litigation paralegals rely on rapid keyword queries to locate critical terms across tens of thousands of exhibits.

NetDocuments' official rollout documentation confirms that files exceeding the two-gigabyte threshold do not currently support several core platform capabilities:

* **Full Text Indexing:** Files exceeding the threshold bypass the search indexer. Attorneys searching for specific Bates numbers, testimony names, or financial terms will never surface matches contained within these oversized documents.

* **Optical Character Recognition (OCR):** Scanned PDF record bundles, trial transcripts, and image sets larger than the standard limit receive no automated OCR processing, leaving them as static, unsearchable bitmaps.

* **Data Loss Prevention (DLP) Tagging on Download:** NetDocuments cannot apply DLP security tags to downloaded files that exceed the threshold, creating a blind spot in matter compliance tracking.

* **Microsoft Information Protection (MIP) Integration:** Advanced sensitivity labels and cryptographic protection policies tied to Microsoft Purview cannot be evaluated on files above the standard limit.

These exclusions create an operational dilemma for litigation practices. Storing an unindexed multi-gigabyte surveillance recording or forensic disk archive inside NetDocuments consumes firm storage allocations without providing searchability or automated governance. Furthermore, when paralegals attempt to send these documents to expert witnesses or co-counsel through native tools like Deliver Secured Link, recipients frequently encounter download timeouts on standard office connections. Legal technology leads must recognize that pushing oversized files into NetDocuments treats an advanced document repository as a basic file locker while stripping away the governance features that justified the platform in the first place.

## Comparing Document Size Limits Across Legal Management Systems

Document size ceilings vary across legal technology providers. Understanding how NetDocuments compares with peer platforms helps legal technology decision-makers design storage policies that match their litigation demands.

| Platform / System | Maximum Document Upload Limit | Supported Upload Methods | Search and Governance Constraints | Date Verified |
| :--- | :--- | :--- | :--- | :--- |
| NetDocuments (Standard) | 50 GB (2 GB default across general web UI) | List-view drag-and-drop, ndOffice 4.2+, multipart API | Files over 2 GB lose full-text indexing, OCR, DLP tagging, and MIP | September 2026 |
| NetDocuments (CMEK / FlexStore) | 2 GB hard limit | Standard web interface, ndOffice | Files capped at 2 GB; large file toggle disabled | September 2026 |
| iManage Work | 5 GB (configurable administrative threshold) | iManage Work web, Work Desktop, File Transfer tool | Web editing tools cap Word/Excel at 100 MB and PowerPoint at 300 MB | September 2026 |
| OpenText eDOCS | 2 GB default document profile limit | eDOCS DM desktop extensions, web client | Large files degrade SQL index performance without separate document caching | September 2026 |
| Fast.io Workspaces | No single-file limit via chunked transfers | Web browser, desktop tools, consolidated MCP tooling | Full-text and semantic search indexing, typed extraction via Metadata Views | September 2026 |

As the comparison indicates, legal document management software platforms are engineered primarily around structured work product such as briefs, contracts, memos, and correspondence. These text-centric files rarely require heavy bandwidth. When systems encounter modern electronic discovery exports, drone surveillance footage, or high-resolution courtroom graphics, their architecture strains under the payload.

Consumer cloud storage services like [Dropbox](/alternatives/dropbox/) and [Box](/alternatives/box/) support larger files, but they lack legal matter folder hierarchies, audit trails tailored to litigation custody, and native document data extraction. For comprehensive matter governance, law firms need a dual-tier storage strategy: keep core legal pleadings and correspondence inside NetDocuments, while routing heavy multimedia archives into a dedicated workspace architecture designed for high-capacity transfer and automated data extraction.

## How to Store and Link Files That Exceed NetDocuments Limits

When a litigation exhibit, medical record package, or video deposition exceeds NetDocuments upload limits or requires full search indexing, legal operations teams should follow a structured five-step mitigation procedure.

### 1. Verify Repository Settings and Account Infrastructure

Before troubleshooting an upload failure, verify whether your firm's NetDocuments repository permits files over the standard limit:

* Log in to the NetDocuments web console with Repository Administrator credentials.

* Navigate to Admin Console, then select Information and Settings.

* Locate the repository setting that controls large file uploads.

* Check whether the box is selected. If the option appears greyed out, your firm uses Customer Managed Encryption Keys (CMEK) or FlexStore, which enforces a strict two-gigabyte maximum file size.

### 2. Evaluate Search and Compliance Requirements

If the repository setting is active, determine whether the file requires full-text search indexing or automated OCR. If attorneys must search inside the document text, uploading an oversized file directly to NetDocuments will fail your team's objective, as indexing is automatically disabled for files exceeding that threshold. In such cases, split multi-volume PDF records into smaller segments, or route the raw media to an external workspace that performs automated search indexing.

### 3. Stage Heavy Discovery in Dedicated External Workspaces

For files that cannot or should not be compressed (such as deposition video files, audio surveillance tapes, computer forensic extractions, and complex blueprints), stage the files in a dedicated [Fast.io workspace](/product/workspaces/). Fast.io uses chunked uploads that process large files in discrete data blocks. If a connection drops during the transfer of a large trial exhibit, the upload resumes from the last confirmed block rather than starting over from the beginning.

### 4. Create Scoped, Expiring Client and Expert Portals

Rather than forcing expert witnesses, trial consultants, or co-counsel to create NetDocuments guest accounts, share access through branded [Content Portals](/product/portals/). Legal teams can generate durable File Shares with password protection and automated link expiration dates. External recipients can review records, stream high-definition deposition video directly in their browser without downloading multi-gigabyte files, and upload discovery productions into Receive shares without creating an account.

### 5. Link the External Workspace Inside the Matter Profile

Maintain matter cohesion by creating a reference pointer inside NetDocuments. Generate a standard matter note or profile link document containing the secure share URL for the external workspace. Record the external link within the NetDocuments matter workspace, ensuring that litigation teams know exactly where the full-resolution discovery assets reside while keeping the primary document repository lean and responsive.

## Managing Deposition Video and Heavy Discovery Records in External Workspaces

Managing litigation evidence demands storage technology that handles high-bandwidth media while maintaining precise administrative governance. Pairing an incumbent document repository with [Fast.io for legal solutions](/solutions/legal/) bridges the gap between text-based document management and high-volume discovery archives.

### High-Definition Video Streaming Without Download Delays

The reliance on video evidence presents an acute operational bottleneck in modern litigation. A single day of remote deposition recordings produces dozens of gigabytes of raw video files. Downloading these files locally to an attorney's laptop takes hours, consumes local drive capacity, and introduces compliance concerns when unencrypted files sit in personal download folders.

Fast.io incorporates native HTTP Live Streaming (HLS) for uploaded video files. When an attorney, claims adjuster, or consulting expert opens a shared deposition link, the video streams adaptively in their browser, matching playback quality to available network bandwidth. Reviewers can scrub through hours of testimony instantly without waiting for the full file to download to their local machine.

### Automated Data Extraction with Metadata Views

The volume of legal document productions often arrives as unstructured collections of invoices, purchase orders, medical bills, or financial disclosures. Manually keying this information into spreadsheets introduces human error and consumes dozens of paralegal hours.

With [Metadata Views](/product/document-data-extraction/), legal teams convert document folders into live, structured databases. You define the fields you need in natural language, such as contract effective dates, governing law, indemnification clauses, or invoice line totals. Fast.io matches files in the workspace and populates a filterable, sortable spreadsheet automatically across scanned pages, PDF documents, and image files. When case strategy evolves, team members can add new metadata columns without reprocessing the underlying files.

### Multi-Party Drafting and Real-Time Notes

When litigation teams synthesize exhibit reviews, collaborative workspace tools become critical. Collaborative Notes in Fast.io provide real-time co-editing spaces where attorneys, paralegals, and consulting experts can draft deposition summaries, cross-examination outlines, and exhibit lists simultaneously. Every note is saved with full per-file version history, ensuring that prior revisions remain recoverable throughout the matter lifecycle.

### Controlled AI Agent Access Through MCP

For firms using autonomous agents to summarize depositions or organize production sets, Fast.io provides a consolidated Model Context Protocol (MCP) server running on Streamable HTTP at `https://mcp.fast.io/mcp/tools` with Bearer token authentication. AI agents can read workspace files, query Metadata Views, and organize discovery productions under strict, org-managed access controls. An agent can assemble a trial portfolio in a workspace, verify file structures, and transfer organization ownership to a managing partner when the work is complete.

### Transparent Workspace Subscription Plans

The Fast.io platform operates on transparent subscription tiers designed for legal teams and organizations, starting with a 14-day free trial that requires a credit card. Storage and seats scale across tiers, with monthly credits metering AI operations:

| Subscription Plan | Monthly Rate | Annual Rate | Included Seats | Included Storage | Included AI Credits |
| :--- | :--- | :--- | :--- | :--- | :--- |
| Starter | $29/mo | $290 billed annually | 5 organization seats | 1 TB storage | 300,000 monthly credits |
| Business | $99/mo | $990 billed annually | 20 organization seats | 10 TB storage | 1,200,000 monthly credits |
| Enterprise | $299/mo | $2,990 billed annually | 50 organization seats | 50 TB storage | 4,500,000 monthly credits |

External clients, co-counsel, and expert witnesses who access shared links do not consume user seats and do not require accounts, eliminating per-guest licensing fees for legal matters.

## Frequently asked questions

### What is the maximum file size in NetDocuments?

Documents up to 50 GB can be uploaded to the NetDocuments platform using the drag-and-drop feature in list view or ndOffice. General web interface destinations maintain a two-gigabyte threshold, and the 50GB upload capability is currently unavailable for FlexStore and CMEK users.

### Can you upload video files larger than 1 GB to NetDocuments?

Yes, documents, exhibits, and video files up to 50 GB can be uploaded to the NetDocuments platform using the drag-and-drop feature or ndOffice. However, video files exceeding two gigabytes do not receive search indexing, and streaming playback is not supported natively.

### How do law firms store large exhibits outside NetDocuments?

Law firms store multi-gigabyte exhibits, forensic images, and video depositions in external workspaces such as Fast.io. These workspaces support chunked uploads with no single-file cap, provide adaptive HLS video streaming, extract structured fields with Metadata Views, and allow branded client delivery without per-user licensing fees.

### Why do ndOffice uploads fail on large files?

Uploads through ndOffice fail primarily due to local internet latency, workstation sleep settings, or repository configuration blocks. Because standard transfers lack chunked resilience, any network drop during a multi-gigabyte upload forces the transfer to abort.

### Does NetDocuments OCR files larger than two gigabytes?

No, NetDocuments does not perform optical character recognition or full-text indexing on documents larger than two gigabytes. Files exceeding this threshold are stored without searchable text metadata.

## Sources

- [NetDocuments: Limits Reference Guide](https://support.netdocuments.com/s/article/205217370): Documents, exhibits, and video files up to 50 GB can be uploaded to the NetDocuments platform using the drag-and-drop feature (in the list view of a filter or folder) or via the ndOffice add-in.
- [NetDocuments: 50GB File Upload Limit Rollout FAQ](https://support.netdocuments.com/s/article/NetDocuments-50GB-File-Upload-Limit-Rollout-FAQ): The 50GB upload capability is currently unavailable for FlexStore and CMEK users.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli. MCP setup is at https://mcp.fast.io/docs: Claude and most MCP clients connect to https://mcp.fast.io/mcp/tools, ChatGPT to https://mcp.fast.io/mcp/operations, and coding agents to https://mcp.fast.io/mcp/code.