How to See Photos and Videos in X Replies Without Opening Each Tweet

Photos, screenshots, and short clips attached to X replies do not reliably render as you scroll a thread — many stay collapsed as a thumbnail or blank preview until you tap into that specific reply, which means a photo-heavy thread can mean a dozen separate taps just to see what people actually posted. That gap between "the media exists in the thread" and "the media is visible without extra taps" is what makes screenshot-heavy and clip-heavy threads feel so much slower to read than text-only ones.

Why threads hide their own media

A reply list is built to be fast to scroll, not to display every attachment at full size. X compresses each reply into a compact row so you can move through dozens of them quickly, and a full-size image or an autoplaying video in every row would slow that scroll to a crawl. The tradeoff is that a lot of visual content gets deferred: a thumbnail loads small, a video shows a static frame until tapped, and on a slow connection or a long thread, some attachments do not render at all until the reply is scrolled fully into view.

This is not a bug so much as a design choice that works fine for text replies and works poorly the moment a thread turns into a screenshot dump or a clip reel — the exact shape a lot of the most useful threads take, whether it is a bug report full of error screenshots, a recap thread stitched from short video clips, or a reply chain where half the value is in the images people are reacting to.

The manual way: tapping into each reply

Right now, seeing every photo or video in a reply thread means working reply by reply. You scroll, spot a thumbnail that looks cut off or a video with a paused frame, tap in, wait for it to load full size, then back out and keep scrolling to find the next one. On a short thread with two or three attachments this is barely noticeable. On a fifty-reply thread built almost entirely out of screenshots, it turns into fifty separate round trips, each one pulling you out of the scroll you were in.

Where it breaks down at scale

The manual approach holds up fine for a handful of attachments and falls apart past that. Three things compound on a long, media-heavy thread:

• Every tap resets your scroll. Opening a reply full-screen and backing out can drop you back near the top of the list rather than exactly where you left off, so you re-find your spot after almost every image.
• Loading is inconsistent. Attachments further down a long thread may not load at all until you scroll them into view, so you cannot tell in advance which replies are worth opening and which are still blank placeholders.
• Video adds a second layer of friction. A clip usually needs its own tap to start, sometimes a second tap to unmute, and a third to close it out, compared to one tap for a static image.

None of this is a reading problem you are doing wrong. It is what happens when a feed built for fast scrolling meets a thread where the content is mostly visual.

The SkimFast way

SkimFast opens a post's full reply thread in a popover right in your timeline, with inline media rendered as part of the thread itself rather than something you tap into one reply at a time. Photos and clips show up as you scroll the popover, matched to your theme, so a screenshot-heavy or clip-heavy thread reads at the same pace as a text one.

A quick routine for media-heavy threads

1. If a thread looks text-only, keep reading normally — the manual way is fine when there is little to open.
2. If you spot two or more attachments in the first few replies, treat it as a media-heavy thread and expect the tap-in, tap-out pattern to slow you down the rest of the way.
3. For a bug report or recap thread you expect to be mostly screenshots or clips, open the whole reply thread at once instead of scrolling and tapping piece by piece — the same shift that helps with following a branching conversation once a thread gets complicated.
4. If you are also trying to find one specific image or clip by a name or phrase someone used, pair this with searching inside a long X thread rather than scrolling until you spot it.

Media-heavy threads are not harder to follow because the content is complicated — they are harder because the reply list was not built to show every attachment at once. Reading one reply at a time works fine until the thread is mostly photos and clips, and at that point the tapping becomes the whole task. SkimFast keeps the thread's media in view as you scroll it, so seeing what people actually posted stops costing a separate tap for every reply.