How do I get the most complete and accurate capture?

PostSnag captures the most complete, accurate picture of a profile when you let the page fully load, scroll slowly and steadily from the top, and wait for "Synced" before comparing counts or exporting. Capturing content off a live, scrolling web page is a little different every time; these habits get you the closest, most reliable result and help you recognize what's normal versus what's actually worth a second look.

Before you start

1. Let the profile fully load before you scroll. If you clicked through quickly from another page or another profile, give it a second, or refresh once, so PostSnag has time to start up on that page before you begin.

2. Start from the very top of the profile. Scanning from the top rather than partway down gives PostSnag the best shot at the earliest posts too.

3. If you're viewing the profile from inside a Facebook group, know that the panel shows only that person's posts captured inside that group, separate from their own profile's posts. Open their profile directly at least once if you want their personal feed as well.

While you scroll

4. Scroll slowly and steadily, in one direction. Fast, jumpy scrolling can outrun what Facebook and PostSnag can both load and read in time.

5. Pause briefly on photo, album, and video posts, including Reels. Media loads separately from a post's text, sometimes more slowly, especially for albums with several photos. PostSnag only captures media that has actually finished loading on screen at that moment; pausing gives it time to catch up.

6. Avoid unnecessary trips back up the page. Facebook reloads and redisplays post cards you've already passed, especially when scrolling upward, so PostSnag briefly pauses new counting to avoid mistaking an old card for a new one. This settles on its own, but scrolling down in one steady pass avoids it altogether.

7. Watch the status pill in the panel. It reads "Capturing" while a pass is active and settles to "Synced" once everything has saved.

[Screenshot: The panel mid-scroll, showing the Collected count and the "Capturing" status pill]

Before you compare counts or export

8. Wait for "Synced" before comparing counts, whether against Facebook's own display, the dashboard, or your memory of the profile. The Collected number updates in stages while you scroll and settles once a pass finishes.

9. Export soon after capturing, rather than after a long delay. Facebook serves media through temporary links, and a long gap between capturing and exporting can occasionally affect a thumbnail.

10. Rescan if you scrolled fast the first time. Scroll back over a section that feels thin, or rescan the profile from the top. PostSnag recognizes posts it already has, so this won't create duplicates.

You don't have to finish a scroll in one sitting. If you close the tab partway through, whatever you've captured so far is already saved locally and will still be there, waiting to export, the next time you open that profile.

If a profile's name or photo looks wrong

This is one of the most common things people notice, and it's almost always timing, not a real mismatch. PostSnag reads a profile's name and picture from what's rendered on the page at the moment of capture, so if the page is still loading, if you're viewing someone's profile from inside a group, or if that profile's photo changed recently, the panel can briefly show outdated or mismatched details until the correct version loads and gets saved. Let the page fully load before scrolling, especially right after clicking through from another profile, refresh if you arrived quickly, and rescan and export again if it doesn't correct itself.

If a captured post seems to belong to the wrong profile

A profile's own feed can include posts shared from, or tagging, other people. PostSnag attributes what it captures to whichever profile page you're actively scrolling, so shared or tagged content that appears on that profile's own feed is expected to be captured there too, not a sign of a mix-up. For the cleanest results, capture a profile directly from its own page rather than from a shared link or someone else's feed.

Set the right expectation on post counts

Even a careful, slow scroll can produce a Collected count that doesn't exactly match what Facebook itself shows on a profile. That's normal, not a sign something went wrong. PostSnag counts what it actually captured from your screen, not a number pulled from Facebook's own backend, and Facebook's displayed counts can be rounded, cached, or affected by that profile's privacy settings. A close, reasonable match is the healthy outcome to expect, not an exact one down to the post.

Common questions

Why doesn't my Collected count match the number Facebook shows on the profile?
PostSnag counts what it actually captures from your screen as you scroll, not a number pulled from Facebook's backend. Small differences are normal and expected.

How do I know a capture pass is finished?
Wait for the panel's status pill to read "Synced" instead of "Capturing."

Should I scroll all the way to the bottom of a profile?
Only as far as the post history you care about. PostSnag only captures what loads as you scroll past it.

What if I think I missed some posts?
Scroll back over that section again, or rescan the profile from the top. PostSnag recognizes posts it already captured, so re-scrolling won't create duplicates.

Is it safe to close the tab in the middle of scrolling?
Yes. Whatever you've captured up to that point is already saved locally in your browser and stays there until you export it, even across browser sessions.