Why didn't a photo, album, or video fully capture?

PostSnag captures a post's photo, album images, and, for videos and reels, the real playable video file plus a cover image, only once that media has actually finished loading on your screen. Media tends to load into Facebook's page separately from a post's text, and more slowly, so a photo, an album image, or a video can come up missing or incomplete if it hadn't finished loading at the exact moment PostSnag read that post. Scrolling a little slower on media-heavy posts is the single biggest thing you can do to close this gap, and a rescan almost always fills in whatever was missed the first time.

This now includes real video. PostSnag saves the actual playable file behind every reel and video it captures, along with a cover image and the clip's duration, not a cover image standing in on its own. If a video post shows only a cover image with nothing playable attached, that's the same kind of loading gap as a missing photo, not a different problem, and the same fixes apply.

Why this happens

• Media loads on a delay. A post's caption and stats are usually available right away, but its photo, album images, video file, or cover image can take a moment longer to load in, especially on a fast scroll or a slower connection.
• Albums have more to load. An album with several photos has more images competing to finish loading at once, so it's more likely than a single-photo post to have one or two images still loading when you scroll past.
• A full video file has more to load than a still image. Capturing the actual video, not just a cover image, means there's more data for the page to finish loading before PostSnag can read it. Giving a video or reel post an extra beat matters more now than it used to.
• PostSnag only captures what's actually finished loading. PostSnag reads media it can see has rendered at that moment. Anything still loading when that post is captured can be missed on that pass, even if it finishes loading a second later. It doesn't go back and check the same post again on its own unless it's scrolled back into view or the profile is rescanned.
• Media links can be temporary. Facebook serves images through links that don't stay valid forever, so a long gap between capturing a post and exporting it to your dashboard can occasionally affect a photo or a cover image. Exporting soon after capturing is good practice for any post.
• Very large albums have a cap. PostSnag stores up to 20 images per album post. If a specific album has more photos than that on Facebook, the images beyond the first 20 captured aren't included, by design, not because they failed to load.

What to do

1. Scroll slowly, pausing briefly on photo, album, and video posts so every image and the full video file have time to finish loading before you move past them.
2. Rescan the profile if you scrolled quickly the first time. PostSnag recognizes posts it already has, so a rescan fills gaps in existing posts without creating duplicates.
3. Export to your dashboard soon after capturing, rather than after a long delay, so media links are still fresh.
4. If a video post shows only a cover image with no playable video attached, scroll it back into view or rescan rather than assuming that's expected. The video file itself hadn't finished loading yet.
5. For a very large album, expect up to 20 images to be saved even if the album on Facebook has more; that's a fixed limit, not something a rescan changes.

[SCREENSHOT: A captured video post in the panel showing its cover image and playable video file]

How to avoid it

Slow your scroll specifically over photo, album, and video posts rather than keeping a single fast pace through the whole profile; a beat or two longer per media post is usually enough for it to finish loading, and a full video file benefits from that pause even more than a photo does. On a slower connection, build in a little extra pause throughout. Get in the habit of exporting to your dashboard shortly after a capture session instead of letting captured posts sit for a long time before syncing them up.

[SCREENSHOT: An album post in the panel showing its captured images]

Common questions

Why does my video post only show a cover image, with nothing playable attached?

That means the video file hadn't finished loading when PostSnag read the post. PostSnag captures the real, playable video file for every reel and video, along with its cover image, but scroll it back into view or rescan and it usually comes through.

Does PostSnag capture the actual video now, or just a cover image?

The actual, playable video file, plus a cover image and the video's duration, for both reels and videos. It isn't limited to a cover image anymore.

Why is only part of an album missing, not all of it?

Album images load individually, so it's common for most of an album to capture cleanly while one or two images were still loading at the moment PostSnag read that post. A rescan usually fills them in.

Is there a limit to how many photos an album can save?

Yes. PostSnag saves up to 20 images per album post. An album with more photos than that on Facebook will still capture, just capped at the first 20 images.

Will exporting again fix a missing image or video without rescanning?

Not on its own. Rescan the profile first so PostSnag can read the media once it's fully loaded, then export.

Related articles

• How do I get the most complete and accurate capture?
• How does scroll-to-capture work, and why does scrolling matter?
• What data does PostSnag capture from each post?
• Why is nothing getting captured on a profile?