Does PostSnag slow down Facebook or my browser?

No. PostSnag is built to stay out of the way: it reads posts that are already loading into the page as you scroll your own Facebook session, rather than running separate, heavy processes of its own. If Facebook ever feels slow while you're using PostSnag, the cause is almost always something else going on in your browser, not PostSnag's own capture logic.

Why this happens

PostSnag doesn't fetch anything from Facebook on its own initiative. It reads posts two ways: from the same network responses Facebook's own page is already receiving as you scroll, and from what's actually rendered on the page in front of you. Either way, it's reading data that's already arriving whether PostSnag is there or not. There's no separate polling loop checking Facebook in the background, and no activity at all on a Facebook page you haven't opened.

The panel itself is a small, self-contained overlay that PostSnag adds directly into the Facebook page. It's not Chrome's built-in side panel and doesn't run as a separate browser feature; it only exists on facebook.com pages and has nothing to do on any other site.

When Facebook does feel slow while PostSnag is active, it's usually one of these, all of which would affect you the same way with PostSnag turned off:

• A media-heavy profile. A profile with a lot of photos, albums, or video naturally takes more for any browser to load and render. That's Facebook's own media loading, not PostSnag's capture logic.

• Other extensions running at the same time. Browser performance is shared across every extension active on a tab. A different extension, or several running together, is a more common source of slowdown than PostSnag by itself.

• Too many open tabs, especially other Facebook tabs, each of which uses its own share of memory regardless of PostSnag.

• An older device or a slow connection, which shapes how any long scroll session feels far more than which extensions you have installed.

What to do

1. Close and reopen the panel. This gives it a clean, fresh start on the current page.

2. Check whether other extensions are running alongside PostSnag. Try disabling others temporarily to see if performance changes; that isolates whether PostSnag is actually the cause.

3. Keep PostSnag updated to the latest Chrome Web Store version, since newer versions carry the latest performance improvements.

4. Close unused tabs, particularly other Facebook tabs, to free up memory that any extension, including PostSnag, shares with the rest of your browser.

5. Give media-heavy profiles a little extra time to load naturally. Scrolling slower on an album- or video-heavy profile helps both Facebook's own rendering and PostSnag's capture.

Keeping performance smooth

Update PostSnag when a new version is available, and avoid running an unusually large number of extensions at once if you're on an older or lower-powered machine. Both of those affect overall browser performance regardless of which specific extensions you use, PostSnag included.

Common questions

Does PostSnag keep running when I'm not on Facebook?
No. Its capture logic only activates on facebook.com pages. It has nothing to do while you're on other sites, and nothing runs in the background for pages you haven't opened.

Will PostSnag slow down websites other than Facebook?
No. PostSnag's panel and capture logic are scoped to Facebook pages only and don't attach to any other site.

Does scrolling faster make PostSnag work harder?
It gives PostSnag less time to read each post before it scrolls off screen, which is more about how complete a capture is than about performance. See "How do I get the most complete and accurate capture?" for the best pace.

Is the panel the same as Chrome's side panel?
No. It's a panel PostSnag builds directly into the Facebook page, not a native browser feature, so browser settings for Chrome's side panel don't apply to it.

What should I check first if Facebook feels slow while using PostSnag?
Close and reopen the panel, then check whether other extensions are running alongside it. Both are more common causes of slowdown than PostSnag itself.