Skip to main content
Troubleshooting

Why is nothing getting captured on a profile?

PostSnag can only capture posts that have actually loaded on your screen, so an unloaded page, a signed-out tab, or an unsupported section can show zero posts collected.

Written By PostSnag

Last updated About 1 month ago

PostSnag shows zero posts collected when a profile page hadn't actually finished loading and rendering posts in your browser at the time you scrolled, or when you're on a part of Facebook PostSnag doesn't capture from. It can only read posts Facebook has already put on your screen, using your own signed-in session; it can't collect anything that isn't actually there to read, no matter how much you scroll.

Why this happens

Capture depends on Facebook's page fully loading and rendering posts as you scroll, in a tab where you're signed in to Facebook itself, and on the profile's main timeline specifically. A few different situations can leave a page without any posts actually rendered for PostSnag to read, or without a feed for PostSnag to read at all:

  1. A slow connection or a page that hasn't fully loaded. If Facebook's own page is still loading in the background, there may be nothing rendered yet, regardless of how much you scroll.

  2. A redirected URL. Occasionally a link redirects to a slightly different page than expected, such as a login prompt or an intermediate page, before landing on the actual profile.

  3. A tab that never came into focus. PostSnag works best on a tab that's open and active while you scroll. A background tab that never gets focus may not behave the same way.

  4. Being signed out of Facebook itself in that tab, which is a separate thing from being signed in to PostSnag. PostSnag needs both.

  5. Being on a profile sub-tab instead of the main timeline. A profile's Reels, About, Photos, and similar sub-tabs aren't the main feed, so PostSnag doesn't capture there; it shows a nudge to head back to the main timeline instead. This includes a person's own Reels tab: their reels are still captured, but from scrolling their main timeline, not from opening that tab directly.

  6. Being on a part of Facebook that isn't a profile, Page, or group at all. Capture is built specifically for personal profiles, Pages, and group member views. Sections like Watch, Marketplace, Events, Notifications, Settings, Facebook's general top-level Reels feed, Stories, Bookmarks, Friends, Jobs, Weather, and Fundraisers aren't post feeds PostSnag reads from, so scrolling one of those will always show zero, by design, not as something to fix.

What to do

  1. Confirm you're signed in to Facebook itself in that browser tab. Being signed in to PostSnag is separate from being signed in to Facebook, and PostSnag needs both to capture anything.

  2. Refresh the profile page, and check that posts are visible on Facebook itself before you start scrolling.

  3. Confirm you're on a profile, Page, or a member's profile inside a group, on its main timeline, not a sub-tab like Reels, About, or Photos, and not a section like Watch, Marketplace, or Notifications. The panel shows a message telling you to switch back to the main feed if you're on a sub-tab of a profile it recognizes.

  4. Scroll slowly from the top of the profile once you've confirmed posts are visible.

  5. Keep the tab focused and active while you scroll, rather than switching to another tab partway through.

  6. Try a different profile you know has posts, to confirm PostSnag is capturing normally in general, then go back to the original profile and rescan.

How to avoid it

Get in the habit of confirming Facebook's own page has actually loaded, with posts visible, before you start scrolling on any new profile. Keep the tab focused while you scroll rather than working in another tab or window at the same time. Scroll a profile's main timeline itself, not a sub-tab like Reels or Photos, since those aren't places PostSnag captures from even when everything else is working normally.

Common questions

Do I need to be signed in to both Facebook and PostSnag?

Yes. PostSnag captures posts from your own logged-in Facebook session, so you need to be signed in to Facebook in that tab, separately from being signed in to PostSnag itself.

It works on other profiles, just not this one. What's different?

Refresh the page and confirm posts are visible on Facebook first, then rescan. A page that loaded in an unusual state is the most common reason one profile behaves differently from another.

Does PostSnag capture from every part of Facebook?

No. Capture works on a profile's, Page's, or group member's main timeline. Sub-tabs like Reels, About, and Photos, and sections like Watch, Marketplace, Notifications, and Stories, aren't feeds PostSnag reads from, so zero posts there is expected.

Does someone's Reels tab count as their profile?

Not for capture purposes. Opening a person's own Reels tab directly shows a nudge to switch back to their main timeline; PostSnag doesn't read that tab. Their reels are still captured, just from scrolling their main timeline, the same way as any other post.

Will PostSnag capture posts if the tab is in the background?

It's built to work best on a tab that's open and in focus while you scroll. If a tab never came into focus, bring it forward, refresh, and scroll again.

Related articles

  • Can I capture Facebook Reels?

  • How does scroll-to-capture work, and why does scrolling matter?

  • How do I get the most complete and accurate capture?

  • What is the PostSnag panel?

PostSnag is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc.