Skip to main content

A Copy That Can’t Be Changed Or Encrypted Later

Some files have to be provable. The day a legal hold starts, the records have to stay exactly as they were that day. After a ransomware incident, you need a copy the malware could not have touched. When you send someone the files as of today, they should download today’s files, not whatever the folder holds tomorrow. A snapshot does all of that: a set of files copied at one moment and then frozen.

You can build a snapshot from files anywhere on your site, including folders you’ve mounted from external storage through Remote Server Mounts, which is how a snapshot becomes an immutable local backup of data that lives in S3 or SharePoint. For ongoing, site-wide rules about how long files live, pair snapshots with data retention and Archive-Only Mode.

How A Snapshot Works

Four steps, and the order is the point: you build it open, then you lock it for good.

Create The Snapshot

Define a new snapshot — give it a name and, ideally, an expiration date. It starts out open, so you can keep building it before you lock it down.

Add The Files

Point the snapshot at file paths from anywhere on your site, including folders mounted from external storage, and Files.com copies them in the background with automatic retries. You can also upload, copy, or move files directly into it.

Finalize It

Finalizing flips the snapshot to read-only. From that moment the contents cannot change, and that is one-way — finalizing cannot be undone. You can still edit the name and expiration date afterward, just not the files.

Let It Expire

Set an expiration date and Files.com automatically removes the snapshot when the date arrives — no manual cleanup. Skip the date and the snapshot stays until you delete it yourself.

What Teams Use Snapshots For

Survive A Ransomware Hit

A finalized snapshot cannot be altered or encrypted after the fact — not by a user, not by an automation, not by malware that gets onto a connected machine. It is a clean, immutable copy of your files as they were the day you took it.

Lock In A Legal Hold

When a hold is triggered, the files have to stay exactly as they were that day. A snapshot captures that state and preserves it — without freezing the working folders or changing anyone’s access in the meantime.

Back Up External Storage

Files in a mounted S3 bucket or SharePoint library might change or disappear in the source system. A snapshot of those mounted files is an immutable local copy on Files.com that does not move when the original does.

Send Files As They Are Today

A snapshot share link sends the files as of the moment you created it, not a live view that shifts as the folder changes tomorrow. The recipient downloads exactly the state you intended to send.

Available On Every Plan

Snapshots ship across Starter, Power, and Enterprise. You can manage them in the app or automate them through the SDKs and CLI — for example, a scheduled job that takes a nightly immutable copy of a critical folder. The broader compliance posture snapshots support, such as Archive-Only Mode and the HIPAA BAA, overlaps with Enterprise-tier features; see what each plan includes on the pricing page.

Compare Plans

Snapshot Questions

What teams ask about immutability, storage, time limits, and automating point-in-time copies.

Capture A Moment You Can Prove

Start a free trial, build a snapshot from any files on your site, and finalize it into a read-only copy that no user, automation, or attacker can change.

No credit card required • Free for 7 days • Live in minutes