Facebook Messenger Export Viewer

Drop in the zip from Facebook's Download Your Information page (or the message_1.json files, or the unzipped folder) and read your Messenger chats with the accents and emoji the way they were sent. The files never leave your computer.

Facebook Messenger Export Viewer

Open the messages from your Facebook data download in the browser. Garbled emoji and accents get fixed, every conversation is searchable, and any chat saves as TXT or CSV. Nothing is uploaded.

Drop your Facebook download zip or message_1.json files here

Several zips or JSON files at once are fine

Your data never leaves your browser. All processing happens locally.

Why your Messenger export looks broken

Open a message_1.json from a Facebook data download in Notepad and you'll probably see something like Jos\u00c3\u00a9 where a friend's name should say José, and a row of \u00f0\u009f\u0098\u0082 where there used to be a laughing emoji. Load it into Python or Excel and it gets worse: you get José and 😂. Nothing is corrupted. Facebook takes the UTF-8 bytes of each character and writes every byte out as if it were a separate Latin-1 character, then escapes the lot. Every program that reads the file correctly, as JSON is supposed to be read, ends up with this mess.

It's been like this for years. There are Stack Overflow answers about it going back to 2018, and pretty much every DIY script on GitHub either trips over it or bolts on a fix that only works in one language. If your chats are in Spanish, Portuguese, Polish, Vietnamese, Arabic or anything with emoji, which is to say nearly everyone's, the raw file is close to unreadable.

This viewer turns every string back into the bytes Facebook meant and decodes them as UTF-8. If the result isn't valid UTF-8, it leaves the text alone, so a name that really does contain é doesn't get mangled a second time. You'll see a count in the stats bar of how many texts it repaired. On a chatty account that number is usually in the thousands.

What you can drop in

If you also have a Telegram Desktop export, the Telegram export viewer opens its result.json with the same search across every chat.

Facebook gives you the export in a few shapes, and the viewer takes all of them:

  • The zip itself, straight from the download page. If Facebook split your export into several zips, select them all at once. The viewer looks for message_1.json, message_2.json and so on inside the messages folder, wherever Facebook put it this year. Older exports have it at messages/inbox, newer ones bury it under your_facebook_activity/messages.
  • The unzipped folder. Use the folder button and pick the folder you extracted. This is the way to go if your download is huge because of photos and videos, since the viewer only opens the small JSON files and ignores the rest. A 15 GB download with years of photos still opens in a few seconds.
  • Loose message_N.json files. Pick one or many. Parts of the same chat are joined back together by the thread path inside each file.
  • The encrypted chat backup from the Messenger app. Chats that switched to end-to-end encryption are no longer in the normal Facebook download; you get them from Messenger's privacy settings as a separate download. Those JSON files use different field names, and the viewer reads those too.

What the viewer shows you

Some of your chats live on WhatsApp instead? The WhatsApp chat analyzer reads WhatsApp's exported .txt file in the browser the same way.

Every conversation appears in a list on the left, newest first, with the folder it came from (Inbox, Archived, Filtered, Message requests or Encrypted chats), how many people are in it and how many messages it holds. Facebook stores long chats newest first and splits them every 10,000 or so messages, which makes reading a conversation in the raw files maddening. The viewer stitches all the parts together and puts them in order, oldest at the top, the way you'd scroll through it in the app.

  • Search covers every conversation at once. Type a word and you get the total number of matches, how many chats they're in, and a list of the actual messages with the hits highlighted. Click one and the chat opens on the right page with that message outlined.
  • Each chat has a who-wrote-what panel showing how many messages each person sent and their share of the conversation. Settling the argument about who always texts first is now a two-second job.
  • Photos, videos, voice messages, GIFs, stickers and files show up as labelled lines with the file name, so you can find the matching file in the export folder.
  • Calls show their length, or say missed call. Shared links show the address and the preview text. Reactions show who reacted and with what. Unsent messages are marked as unsent instead of quietly vanishing.
  • Save the open chat as plain text or CSV. Both use proper UTF-8 with a byte order mark, so Excel opens the CSV with the accents and emoji intact, which is exactly the thing that goes wrong when people try this by hand.

Your messages stay on your computer

I built this to run entirely in the browser because a Messenger export is about as private as it gets. Years of conversations, addresses, phone numbers, the occasional password someone sent you once. The files are read by JavaScript in this tab and that's the end of it. No upload, no account, nothing stored. You can check: load the page, switch off your Wi-Fi, then open your export. It works the same.

Messages are also displayed as plain text. If a friend once sent you a chunk of HTML or a script tag as a joke, you'll see the characters on screen and nothing will run. Shared links are shown as text rather than turned into clickable links, so a dodgy URL from an old group chat can't send you anywhere by accident.

How to get your Messenger data from Facebook

  1. On Facebook, open Settings and go to Accounts Center, then Your information and permissions, then Download your information.
  2. Choose Download or transfer information, pick your Facebook profile, and choose Specific types of information.
  3. Tick Messages. Leave the rest off unless you want it; the download is much smaller and arrives sooner.
  4. Set the format to JSON. This is the step people miss. The default is HTML, and the viewer can't read that.
  5. Pick a date range (All time if you want everything) and set media quality to Low if you only care about the text.
  6. Submit the request. Facebook emails you when it's ready, anywhere from a few minutes to a couple of days later. Download the zip and drop it here.

Who actually uses this

A chat saved as CSV can be sorted and filtered in the CSV viewer without opening Excel.

People deleting their Facebook account who want their conversations somewhere readable first. Someone who lost a parent and wants to keep years of messages with them. Small business owners who took orders over Messenger and need to check what was agreed. People pulling a chat together for a lawyer, a landlord dispute or an insurance claim, where dates and exact wording matter. And plenty of people who just want to see how many messages they and their best friend have sent each other since 2012. That number is usually higher than anyone guesses.

What it won't do

It doesn't display the photos themselves. The JSON holds file paths, not pictures, and loading thousands of images into one tab would make it crawl. The file name tells you exactly which file to open in the export folder. It doesn't open the HTML version of the export, so if you already downloaded HTML you'll need to request the data again in JSON. And it can't bring back messages that were deleted before you made the request. If they weren't on Facebook that day, they aren't in the file. Chats that moved to end-to-end encryption also won't be in the regular download at all, which surprises a lot of people; grab those from the Messenger app separately and add them in.

Frequently Asked Questions About the Facebook Messenger Export Viewer