How to Export Facebook Messenger and Instagram DMs for Court Evidence
Facebook Messenger and Instagram DMs show up constantly in family law cases — co-parents and former partners who'd never willingly text again will still argue over child pickup times in a Messenger thread. Both platforms are owned by Meta, and both export through the same underlying tool, which is why this is one guide instead of two. The two requests are still separate, though, so here's how to get each one right.
What you're actually going after
Meta's "Download Your Information" tool lets any account request a copy of its own data, including message history. There's no button inside a conversation that exports just that thread — instead you submit a request with the settings you want, Meta builds a file, and it notifies you once the file is ready to download.
Getting the file
1.Request your export from Facebook
From Facebook, go to Settings & Privacy → Settings → "Your Facebook Information" → "Download Your Information." Meta's menus move around over time, so if the exact wording looks different, search "download your information" from the Settings search bar.
2.Request your export from Instagram — separately
Instagram is a different request, even though it's the same company. From Instagram, go to Settings → "Your Activity" → "Download Your Information" (on newer versions of the app this may live under Accounts Center → "Your information and permissions"). Requesting your Facebook data does not include your Instagram DMs, and vice versa — if you need both, submit both requests.
3.Pick the date range and the specific conversation
Both tools let you narrow the request instead of exporting your entire account. Choose "All time" if you want the full history of the relationship, or a specific date range if you only need a portion of it. More importantly, select the specific conversation or thread you need rather than "all messages" — this keeps the file a manageable size and avoids pulling in unrelated conversations with other people.
4.Choose a format: JSON or HTML
Meta offers two format options for the export — JSON and HTML. This matters less than it sounds like it should, because Verity reads both directly. Pick whichever one the tool defaults to, or whichever you find easier to work with — see the format section below for what each one actually looks like.
5.Wait for Meta to prepare it
This isn't instant — Meta builds the file as a background job and notifies you (in-app and by email) once it's ready to download from the same "Download Your Information" screen. Facebook's own help documentation notes you'll have a limited window — a matter of days, not weeks — to actually download it once it's ready, so don't let the notification sit unread. If you're working against a filing deadline, request the export as early as possible rather than waiting.
6.Upload the file as-is
Don't retype the conversation or convert it to another format. If you chose JSON and the conversation is long, Meta may split it across multiple numbered files — message_1.json, message_2.json, and so on — so check the folder for additional parts rather than assuming the first file is the whole thing. Upload whichever file(s) you have exactly as Meta generated them.
JSON vs. HTML — the choice that actually matters
This is the one decision in the whole process worth understanding, and the good news is that you can't really get it wrong with Verity.
JSON is the format Meta's export tool structures around each conversation directly — for a single thread, you'll typically get a message_1.json file (or several numbered files for a long conversation) containing a list of every message, each with who sent it, exactly when, and the message text.
HTML is Meta's browsable version of the same data — a page formatted to look like the conversation, meant to be opened in a browser. The catch with HTML exports generally is that the styling comes from auto-generated CSS class names that change between export versions, which makes them fragile for a tool to parse reliably if it's matching against those class names.
Why Verity handles both
Most tools built around one of these exports only handle the format they were originally built for. Verity reads Meta's JSON export directly — pulling the sender, timestamp, and message text straight out of the structure Meta already built. For the HTML export, instead of matching against Meta's auto-generated class names, Verity walks the page structurally: it reads every line of visible text in document order and reconstructs each message from the fixed pattern Meta's HTML export always follows — a sender name, one or more lines of message text, then a timestamp in a recognizable "Mon D, YYYY, H:MM:SS AM/PM" format. Because that pattern doesn't depend on any particular class name, it holds up across different export versions.
Practically, that means whichever format you happened to pick — or whichever one you already have sitting in a downloads folder — works. You don't need to re-request the export in a different format to make it readable.
Keep the request narrow
Both platforms let you select a specific conversation rather than exporting your entire message history. Do that. A single-thread export is faster for Meta to prepare, easier to handle on your end, and it keeps conversations with other people out of a file you're about to hand to an attorney.
How this stays private
Verity reads the JSON or HTML file directly in your browser — the same privacy model as every other format the site supports. The conversation itself is never uploaded to a server; only the resulting health score and pattern metadata leave your device once you choose to generate a report.
This is general information, not legal advice. Verity is not a law firm, and requirements for authenticating a digital record vary by court — talk to an attorney about what your case specifically needs.
Already have your Facebook or Instagram export?
Upload the JSON or HTML file and get a free health score in minutes — parsing happens entirely in your browser.
Analyze your export →