Does PostSnag work on non-English Facebook?

Yes. PostSnag reads posts by their structure, post type, media, and engagement numbers, not by the language they're written in, so it works the same way no matter what language your Facebook is set to.

Why this happens

PostSnag decides what kind of post it's looking at by checking a set order of structural signals on the page: whether it's a reel, then a video, then an album of several images, then a single photo, then an external link, and finally plain text if none of those match. None of those checks depend on understanding the caption's language; they're based on layout, media elements, and the post's own underlying data, the same across any language or locale.

Engagement numbers (reaction counts, comments, shares, video views) work the same way: PostSnag reads the actual numbers on the page, not text describing them. Captions are captured and stored exactly as posted, in their original language and script, with no translation applied at any point.

One detail is genuinely language-dependent: relative timestamps. When Facebook's own exact date and time are available on the page, PostSnag uses that directly. When only a relative time is showing, something equivalent to "2h" or "3d" in whatever language your Facebook is set to, PostSnag converts it into an exact date and time. That conversion is built to work across languages, but it's the one place where the page's language actually matters, so it's worth a quick spot check on a locale you're less familiar with.

Worth knowing separately: the PostSnag panel and dashboard interface themselves, the buttons, labels, and menus you interact with, are in English today. That's about the tool's own interface, not a limit on which Facebook language or region you can capture from.

Exporting works the same way too. A Markdown or CSV export keeps non-English captions, accented letters, and non-Latin scripts exactly as captured, so opening the file in a spreadsheet or pasting it into an AI tool shows the original text, not placeholder characters or a broken translation.

[Screenshot: Hovering over a post's timestamp on Facebook to reveal its exact date and time]

What to do

1. Capture normally. There's no setting to change or mode to switch on for a non-English profile; scroll and export the same way you would in English.

2. Spot check a timestamp if you're capturing an unfamiliar language for the first time. Hover directly over a post on Facebook to see its exact date and time, and compare that against what PostSnag captured.

3. Review captions in your dashboard as needed. They'll display in their original language and script exactly as posted, with no translation to account for.

4. Treat any other odd result the same as you would in English. If a post's type or details ever look off regardless of language, the usual troubleshooting steps, rescanning, letting the page fully load, apply the same way.

A good habit for unfamiliar languages

The first time you capture a profile in a language you don't read, spot check a handful of dates and post types against the original Facebook posts. Once you've confirmed a few line up, the same structural capture applies consistently on every profile after that, in any language.

Common questions

Do I need to change any settings to use PostSnag on non-English Facebook?
No. PostSnag works the same way regardless of your Facebook language setting, with nothing to switch on or off beforehand.

Will exported captions be translated into English?
No. Captions are captured and exported exactly as posted, in their original language and script.

Is capture equally accurate on every language and writing system?
Capture is built to work the same way regardless of language or writing direction, since it identifies posts by structure, not text. Relative timestamps are the one detail worth spot checking on a locale you're less familiar with.

Is the PostSnag interface itself available in other languages?
Not currently. The panel and dashboard are in English. This only affects the labels and buttons you interact with, not which Facebook language or region you can capture from.

Why would a captured date ever look slightly off on a non-English profile?
Usually because it came from a relative time ("2h," "3d," or the equivalent) that had to be converted, rather than an exact timestamp already on the page. Hovering the post on Facebook shows its exact time for comparison.

Will accented letters or non-Latin scripts show up correctly in an export?
Yes. Markdown and CSV exports keep captions exactly as captured, including accents and non-Latin scripts, so the original text carries through rather than being altered or stripped.