How to Preserve Facebook Posts as Evidence (2026 Guide)

October 12, 2026

Facebook is still where a great deal of evidence lives: the post that contradicts a disability claim, the comment thread at the center of a defamation suit, the photo that places someone at a party they swore they missed. Every one of those can be hidden, edited or deleted by its author in seconds, and the company that runs the servers will not hand its content to you in a civil case.

The short answer: capture the post at its own address, with a neutral automated system that records the time and process and fingerprints the result, before it changes. The rest of this guide explains why each part of that matters for Facebook in particular: how posts change or disappear, why a subpoena to Meta will not bring them back, and what courts look for when a Facebook post is offered. For the principles that apply to every platform, see our guide to preserving social media evidence.

How Facebook posts change or disappear

Each of these is documented by Meta itself.

The audience can shrink after the fact. Facebook says plainly that “after you’ve shared a post, you have the option to change who it’s shared with,” down to Friends or Only Me. The post still exists in the owner’s account. You just cannot see it anymore.

Posts and comments can be edited. Authors can edit their own posts and comments after publishing. For posts on a Facebook Page, Meta says anyone who can see the post can also see its history of edits. Meta does not document the same for posts on a personal profile, so do not count on an edit trail being there when you need it.

Posts can be archived or sent to Trash. An archived post becomes visible only to its owner, and can be restored later. A deleted post goes to Trash, where it stays for up to 30 days before it is deleted automatically and can no longer be restored, unless the owner empties it sooner. From your side of the screen, either way, the post is simply gone.

Stories last 24 hours. After that, a story survives in its author’s private archive, if they have one switched on, unless they feature it on their profile.

Whole accounts go dark. A deactivated account hides its profile (“no one else can see your profile”) without deleting it. A deleted account can be restored for 30 days (Meta says the window varies by region), and Meta says removing its posts can take up to 90 days. Either way, almost nothing on it is visible to you in the meantime.

Meta removes accounts at enormous scale. In the second quarter of 2026 alone, Meta took action on 822.4 million fake Facebook accounts, according to its Transparency Center. A post you need can disappear with an account because of an enforcement decision that nobody in your case made.

Why a subpoena to Meta will not save you

Many lawyers assume that if a post disappears, Meta can be made to produce it. In a civil case, you generally cannot make Meta produce the content of a post, and Meta says it cannot restore deleted content.

Meta’s help page on subpoenas puts the first part directly: “Private parties cannot obtain the contents of Facebook accounts using subpoenas under federal law.” The federal law is the Stored Communications Act, which bars providers from disclosing the contents of communications except in narrow cases (18 U.S.C. § 2702). Courts have enforced that against civil litigants, for example in Crispin v. Christian Audigier, Inc., 717 F. Supp. 2d 965 (C.D. Cal. 2010), which quashed civil subpoenas to Facebook and MySpace for users’ private messages. Meta may provide basic subscriber information on a valid subpoena, but not what was posted.

Law enforcement has more reach, but not much more help for you. Meta’s law enforcement guidelines require a search warrant for the stored contents of an account, and its 90-day preservation holds are for official criminal investigations only.

What Meta points to instead is the parties themselves: account holders meet their discovery obligations by producing their own content, using Facebook’s Export your information tool, in HTML or JSON. That means a post the other side narrowed to Only Me or archived can still be demanded from them in discovery, and a court can compel them to produce it. What discovery cannot give you is the version you saw before it was edited, a post that has already been emptied from Trash, or confidence that what comes back is what was public on the day it mattered. A capture fixes what was public, and when, without depending on the other side.

A preservation demand is still worth sending early, because destroying evidence once litigation is foreseeable has consequences. In Gatto v. United Air Lines, Inc., No. 10-cv-1090 (D.N.J. Mar. 25, 2013), a plaintiff deactivated his Facebook account during discovery, the account was then permanently deleted, and the court gave the jury an adverse-inference instruction. Since the 2015 amendments to Federal Rule of Civil Procedure 37(e), a federal court needs a finding that a party intended to deprive the other side of the information before giving that instruction for lost electronic evidence. In Allied Concrete Co. v. Lester, 736 S.E.2d 699 (Va. 2013), the trial court sanctioned a lawyer $542,000 and his client $180,000 after the lawyer, through his paralegal, told the client to “clean up” his Facebook page. But a sanction punishes the other side. It does not bring the post back. A capture does.

What courts look for in Facebook evidence

There is no special rule for Facebook. Courts apply the ordinary authentication standard (in federal court, Federal Rule of Evidence 901). Two questions decide most disputes: who wrote it, and has it changed.

Who wrote it. In United States v. Farrad, 895 F.3d 859 (6th Cir. 2018), Facebook photos came in because they showed the defendant, his tattoos and his apartment, details the police confirmed independently. In United States v. Barnes, 803 F.3d 209 (5th Cir. 2015), Facebook messages were tied to a defendant by a witness who had seen him use Facebook, recognized the account, and said the messages matched how he wrote. In Parker v. State, 85 A.3d 682 (Del. 2014), the Delaware Supreme Court upheld the admission of a defendant’s Facebook post, holding that circumstantial evidence can authenticate social media and rejecting a stricter standard some courts had used. Where nothing ties the account to the person, the evidence fails: in Commonwealth v. Mangel, 181 A.3d 1154 (Pa. Super. Ct. 2018), messages and posts from an account bearing the defendant’s name were excluded because nothing tended to “corroborate the identity of the author.”

A Facebook certificate does not answer that question. In Farrad, the Sixth Circuit held it was error to treat the photos as self-authenticating on the strength of Facebook’s records certificate; the error was harmless only because the photos were authenticated under Rule 901 anyway. United States v. Browne, 834 F.3d 403 (3d Cir. 2016) reached the same point with Facebook chats. A platform can certify that an account sent something at a time. It cannot certify who was typing. Our guide to FRE 901 vs FRE 902 explains why.

Has it changed. A screenshot of a Facebook page with nothing behind it is easy to attack. In Moroccanoil, Inc. v. Marc Anthony Cosmetics, Inc., 57 F. Supp. 3d 1203 (C.D. Cal. 2014), screenshots of Facebook pages were excluded for lack of authentication. A capture that records its own address, time and process, and fingerprints its files when it is made, answers the second question before anyone asks it.

How to preserve Facebook posts as evidence, step by step

1. Move first, and triage by risk. Stories go first: the 24-hour clock is running. Then posts from accounts likely to change their audience, deactivate, or delete once a dispute is in the air.

2. Capture the post’s own address, not your feed. Facebook’s method for finding a post’s link is to click the date or time shown on the post, which opens the post on its own page. The same works for an individual comment. Capture that page, with the account name, date and comments in view.

3. Capture the context too. The profile or Page that published it, and the comment thread under it. For a Page post, the edit history opens from the post’s menu, so record that view yourself as described below. A post without its author and surroundings invites the authorship fight described above.

4. Let a neutral process make the record. The capture should record its own address, time and process, and fingerprint every file with a cryptographic hash at capture. That is the record a certification under FRE 902(13) and 902(14) describes, and it keeps you out of the chain of custody for your own exhibit. It shows the capture is accurate, not who wrote the post, so you still need Rule 901 evidence of authorship.

5. Preserve what you can see, demand the rest. Capture what is visible to you now. Send a preservation demand for what is not, and ask in discovery for the account owner’s own export.

Private profiles, private groups and Messenger

Facebook’s privacy settings decide what you can capture yourself. Friends-only posts, private groups you do not belong to, and Messenger conversations are out of reach, and the shortcuts are traps: do not send, or have anyone send, a friend request to a represented party, and do not use deception to friend anyone. Ethics rules on contacting represented parties apply online as they do anywhere else. For that content, a preservation demand keeps it, and discovery or someone entitled to see it produces it.

Preserving Facebook evidence with Permavault

Paste a Facebook post’s address into Permavault and a neutral automated system opens it in a browser, preserves the page as it rendered, fingerprints every file with cryptographic hashes at capture, and stores the result on a permanent decentralized network of roughly 300 independent nodes, funded by a long-term storage endowment. The capture records its own address, time and process, and it and its proof are designed to stay retrievable and verifiable without depending on any vendor. Including us.

Permavault opens the post the way a signed-out visitor sees it, and Facebook may show signed-out visitors a sign-in prompt or only part of a page. When a public post, or the comments under it, only show in full after signing in, record the page from your own real account, never a fake or borrowed one, with Webrecorder’s free ArchiveWeb.page browser extension, which exports it as a WACZ web archive, and upload that file. The same route records a Page post’s edit history. Permavault checks the archive, brings it to the WACZ standard, and fingerprints and seals the result, so keep your original export too. Archives up to 10 MB can be held free for 7 days and cost $0.99 to make permanent, which is when the independent timestamps are added, so do it the same day if timing matters; larger archives are priced like any other file. Two trade-offs come with it. The archive shows your signed-in view, including your own account, and anyone with a regular capture’s link can view it. And the certificate records it as a user-supplied archive, so whoever recorded it may need to testify about how: have an investigator or paralegal make it, not trial counsel. Where the post loads without signing in, let the server capture it and stay out of the chain of custody.

Each capture is $4.99, down to $2.98 with a pack, and carries an independent Bitcoin-anchored timestamp. An optional $9 Certificate of Authenticity documents the capture process. The Legal certificate ($39) adds an RFC 3161 timestamp on the signed capture manifest, a chain-of-custody appendix, and a declaration template designed to support authentication under FRE 902(13) and 902(14). The Legal evidence package states whether the timestamp qualifies under eIDAS.

The post that is public today can be Friends-only by tonight. The version of record is the one you captured.

This article is general information, not legal advice for any specific matter. Preservation obligations and admissibility depend on the facts, the jurisdiction, and the judge. Facebook feature descriptions reflect Meta’s published help content as of October 2026.