Hyperlinked Files, Cloud Collaboration, and the New Geometry of Preservation Obligations

The conventional email attachment is giving way to the link. In Microsoft 365, Google Workspace, and collaboration platforms like Slack, employees increasingly share documents by pasting a link to a file that lives in a cloud repository rather than attaching a copy. This shift, designed to make collaboration easier, has created one of the most heavily litigated questions in electronic discovery: when an email links to a cloud document rather than attaching it, is that linked document an attachment that must be preserved and produced as part of the same family?

The answer, as the case law now makes clear, is not automatic. Courts have declined to treat a hyperlink as the equivalent of an attachment by default, and they resolve the question through proportionality, feasibility, and the governing ESI protocol. For a corporate defendant, this is both an opportunity and a trap. A well-negotiated protocol and a defensible preservation approach can contain the burden, while an ill-considered agreement or a preservation gap can generate disproportionate cost and sanctions exposure. This paper explains the doctrine, the distinctive versioning problem, and how to frame a defensible position before that exposure accrues.

A Hyperlink Is Not Automatically an Attachment

The foundational principle emerging from the case law is that a hyperlink relationship does not, by itself, make the linked document a conventional attachment. An email and the file it attaches form a document family that travels together in discovery. A link is different in kind: it is a pointer to a document stored elsewhere, often in a live repository where the document may change over time.

Courts have repeatedly drawn this distinction. In Yotta Technologies Inc. v. Evolve Bank & Trust, 2026 WL 172502 (N.D. Cal. Jan. 22, 2026), the court declined to compel production of hyperlinked documents on the theory that the link alone made them attachments, agreeing that a hyperlink relationship does not by itself mean the linked document should be treated and produced as an attachment. The court drew on earlier authority, including In re Meta Pixel Healthcare Litigation, 2023 WL 4361131 (N.D. Cal. June 2, 2023), where the court indicated that an ESI protocol should make clear that hyperlinked documents are not treated as conventional attachments, weighing proportionality, cost, and delay.

This does not mean linked documents are beyond discovery. A linked document that is relevant remains discoverable like any other ESI. What the case law rejects is the automatic family treatment that would require every linked document to be collected, version-matched, and produced alongside the email that referenced it, regardless of burden. The distinction matters enormously, because automatic family treatment across a large cloud-collaboration environment can impose extraordinary cost.

The Versioning Problem

Even where a linked document must be produced, a distinctive technical problem arises that has no analog in conventional attachments. A traditional attachment is frozen at the moment it is sent. A linked cloud document is not. It lives in a repository where it can be edited after the link is shared, so the version a recipient saw when the link was sent may differ from the version that exists when the document is later collected.

Commentators have called this the reassembly or versioning challenge: the difficulty of reuniting a link with the specific version of the target document that existed at the moment the link was shared. Doing so requires capturing point-in-time versions from authenticated, permissioned cloud repositories, a task that depends heavily on the capabilities of the specific platform and the tools available to the producing party.

Courts have approached this practically. Some have ordered narrow, sampled efforts rather than wholesale reassembly. In at least one matter, a court directed the producing party to select a defined set of responsive emails with hyperlinked attachments and run a specialized collection tool against them within a fixed period, a targeted approach rather than a blanket requirement. This reflects a judicial willingness to test feasibility and proportionality before imposing a sweeping obligation.

Proportionality and the ESI Protocol

The governing framework is proportionality under Rule 26(b)(1), applied through the ESI protocol the parties negotiate under Rule 26(f). Courts assessing hyperlinked-document disputes ask whether the tools to maintain link-to-target relationships are feasible in the producing party's actual environment and, if feasible, whether their use is proportional to the needs of the case and not unduly burdensome. Where the answer is no, courts have declined to impose the obligation.

Negotiate the protocol with technical reality in view. The most consequential decisions about modern attachments are made in the ESI protocol, often before the producing party fully understands its own collection capabilities. A party that agrees to treat hyperlinked documents as attachments, then discovers its tools cannot feasibly do so, faces a difficult position. The lesson from the case law is to understand collection capability before agreeing to a standard, not after.

Preserve the ability to amend for good cause. Even a carefully negotiated protocol can encounter unforeseen technical limitations. Parties that preserved the option to modify the protocol for good cause have been able to adjust when reassembly proved infeasible, while parties locked into an unworkable standard have faced substantial delay and dispute in seeking relief. A good-cause amendment provision is a critical safeguard.

Distinguish internal links from external and third-party links. Not all links are alike. A link to an internal, controlled repository raises different feasibility and control questions than a link to a document held by a third party, where the producing party may lack possession, custody, or control. Courts have addressed the obligation to pursue linked files from non-parties as a distinct question, and the protocol should reflect these different categories rather than treating all links uniformly.

Preservation Obligations and Sanctions Exposure

The production question is downstream of a preservation question, and the preservation question is where sanctions risk concentrates. The duty to preserve relevant ESI attaches when litigation is reasonably anticipated, and it reaches the cloud repositories where linked documents live. Because those repositories are dynamic, a document that is edited or deleted after the duty attaches can become the subject of a spoliation dispute.

Rule 37(e) governs the consequences of failing to preserve ESI that should have been kept. Its most serious sanctions require a finding that a party acted with the intent to deprive another of the information. A company that took reasonable steps to preserve relevant cloud documents, even if some versions were lost to ordinary system operation, is positioned to resist the harshest sanctions by demonstrating the absence of intent to deprive. The defensibility of the preservation effort, documented contemporaneously, is what carries that argument.

The geometry of preservation has genuinely changed. A legal hold drafted for a world of email attachments may not reach linked cloud documents, point-in-time versions, or the permissioned repositories where collaborative files live. Holds must be designed for the actual data environment, naming the cloud platforms and the versioning concerns expressly, so that the company can show it took reasonable steps appropriate to the systems it actually uses.

A Defensible Approach

Managing modern-attachment risk is a matter of preparation across the life of a matter. The following measures reflect a disciplined approach that keeps a defendant ahead of the exposure.

Understand collection capability before the protocol negotiation. A producing party should know what its tools can do in its specific environment before agreeing to any hyperlinked-document standard. Our discovery strategy and management teams assess collection feasibility across a client's collaboration platforms early, so that protocol positions are grounded in technical reality rather than aspiration.

Coordinate the approach across related matters. For companies facing multiple matters or large consolidated dockets, a consistent and defensible modern-attachment position avoids the contradictions that arise when different cases adopt different standards. Our class action and MDL teams coordinate ESI-protocol strategy across related litigation so that the producing party's capabilities and commitments remain consistent.

Build holds and preservation around the real environment. A preservation approach that names the cloud platforms, addresses point-in-time versioning, and documents reasonable steps is what defeats a later spoliation argument. Our pre-litigation counseling teams help companies design holds and preservation protocols for their actual collaboration environment before litigation, so that the reasonable-steps showing under Rule 37(e) rests on a contemporaneous record.

Conclusion

The migration from attachments to links has reshaped the geometry of preservation and production. Courts have settled on a sensible default, that a hyperlink is not automatically an attachment, and they resolve the harder questions through proportionality, feasibility, and the ESI protocol. For a corporate defendant, the exposure is real but manageable. The decisive moments come early: understanding collection capability before negotiating the protocol, preserving the ability to amend for good cause, distinguishing internal from third-party links, and building holds that reach the dynamic cloud repositories where collaborative documents live. A company that addresses modern attachments deliberately, before a dispute crystallizes, heads off the disproportionate cost and sanctions exposure that overtake those who treat the link as an afterthought.