Convert Facebook Messenger chats to PDF
Updated
Facebook’s data download gives you Messenger conversations as message_1.json files — raw JSON with no layout, broken accented characters, and long threads split across several numbered files. Chat to Evidence reads that export and produces an actual document: a chronological transcript with timestamps, sender names, day separators and page numbers.
The conversion happens entirely in your browser tab. Messenger histories can span years of personal conversation, so nothing about the file is ever sent anywhere — the only network calls are for font files.
How to convert Messenger chats to PDF
- Download your Messenger data from Meta first — see How to download Facebook Messenger history for the exact Accounts Center steps.
- Unzip the download and open your_facebook_activity/messages/inbox/<conversation name>/, where you’ll find message_1.json (and message_2.json, message_3.json, etc. for longer threads).
- Open chattoevidence.com and drop message_1.json in. If a conversation spans multiple numbered files, drop the whole download .zip (or zip that conversation’s folder) so the tool can find and merge them all.
- Review the preview for the right participant names, correct date range and readable text. Rename anyone whose Facebook name should appear differently in the PDF.
- Click Generate PDF. The free version shows the first 100 messages with a watermark; the $9 Case Pass unlocks the whole conversation and adds the certification page with source-file hashing.
Why the raw export isn’t usable on its own
message_1.json is structured for programs, not people: a `messages` array where each entry carries a `sender_name`, a `timestamp_ms` (milliseconds, not a normal date), and a `content` field, with reactions, shared photos, links and calls each represented differently. There’s also a well-known text-encoding bug in Meta’s export — accented letters, non-English words and emoji come out as scrambled characters (mojibake) because the JSON declares UTF-8 but the text inside is escaped as Latin-1.
Chat to Evidence converts the millisecond timestamps to readable dates and times, reconstructs correctly encoded text automatically, and separates actual messages from system events like “X named the group” so the transcript reads like a real conversation.
What the finished PDF includes
A cover page states the conversation name, participants, date range and total message count. The transcript lists each message with its exact time, the sender’s name, and the text, with a line break at each new day. Every page carries a footer with “Page X of Y”, so a printed or scanned copy can’t quietly lose a page in the middle.
The Case Pass adds a certification page recording the SHA-256 hash of the exact JSON file(s) used, so the PDF can be tied back to an unaltered source file, plus optional exhibit labeling and Bates numbering across the document.
Group conversations and merged files
Group Messenger threads use the same file structure with more senders listed; each person’s name appears correctly next to their messages. For any single conversation, Meta numbers the files in reverse order (message_1.json holds the most recent portion), so for a long-running chat drop the whole download .zip (or a zip of the conversation folder) and the tool reconstructs the entire history in the right order.
When you need a Messenger transcript
A properly formatted transcript is often what’s actually requested for an HR complaint, a small-claims filing, a landlord dispute or a visa relationship-evidence package — a document with clear dates, not a folder of screenshots. See Chat evidence for a small-claims case and Chat evidence for an HR complaint for how the same document format applies once it’s in PDF form.
Frequently asked
Do I need message_1.json specifically, or a different file?
message_1.json (and message_2.json, message_3.json, … for longer threads) is the file to use. For the complete history drop the whole download .zip, or a zip of the conversation folder.
My messages show odd symbols where accents or emoji should be.
That’s a known encoding issue in Meta’s export format, affecting everyone’s downloads, not something wrong with your data. Chat to Evidence detects and repairs it automatically when the file is parsed.
Can I convert a Messenger group chat, not just a 1:1 conversation?
Yes. Group threads export the same way with additional participants listed; each sender’s name is attached correctly to their own messages.
Does this include calls and video chat history?
Call events appear in the JSON as short entries (call started/ended) and the tool includes them as system lines in the transcript, but there’s no audio or video content in a data export — only the message and event log.
Chat to Evidence is a document-formatting tool, not a law firm. Nothing on this page is legal advice; rules and app menus change, so check current official guidance.