Project Hail Mary Is on Prime Video Today. The Space Scenes Are a Screenshot Nightmare — Here's Why.

Project Hail Mary hit Prime Video today. The film earned $683 million theatrically — third-biggest of 2026 so far — and spent its post-theatrical window on MGM+ before unlocking for Prime subscribers this morning. Ryan Gosling's performance as Ryland Grace, the amnesiac science teacher who wakes up alone on a spacecraft with a mission to save Earth, was the consensus best actor performance of the spring release season.

The visual effects held up from theatrical. The alien Rocky, the film's other lead (and entirely a VFX creation by WETA Digital), looks as convincing on a home screen as it did on IMAX. The spacecraft interior design — cramped, warm, functional — is the kind of practical-feeling sci-fi set that rarely translates well to streaming compression, but it does here.

The problem is what happens when people screenshot and share those visuals.

What Makes Space Cinematography So Hard to Compress

The film's director of photography shot the space-set sequences around two fundamental visual choices: pure black for the void (not dark blue, not dark gray — black), and highly saturated, luminous sources for everything else. Rocky's bioluminescence. The spacecraft's running lights. The distant star Tau Ceti.

These choices make for extraordinary cinematography and genuinely terrible compression conditions.

JPEG was designed for images with natural luminance gradients — the way light falls off across a face, the way sky transitions from blue to white at the horizon. It handles those transitions efficiently because it can encode them as smooth, predictable DCT coefficients. What it handles badly is point-light sources against pure black: a bright, saturated, radially-glowing object in the middle of an otherwise empty dark frame.

This is exactly what Rocky looks like in every scene.

The bioluminescent patterns on Rocky's body form radial pulses — rings of light that spread outward from the creature's surface. JPEG encodes these in 8×8 pixel blocks, and each ring crosses multiple block boundaries at angles. At each boundary, JPEG introduces a ringing artifact: a faint dark halo visible just outside the bright ring, and a faint bright halo just inside the dark area beyond it. The effect is subtle on a single bright ring; Rocky has dozens, at multiple scales, pulsing at different intensities. The accumulation of ringing across all those rings produces a visible shimmering artifact structure around the creature.

Why the Interior Scenes Compress Completely Differently

The spacecraft's interior — the sleeping quarters, the lab area, the corridor where Grace works out while trying to remember who he is — uses a very different color palette than the space exterior sequences. The production designer lit the ship with warm amber sources: practical desk lights, amber LED strips along the walls, warm fluorescent equivalents in the ceiling. The overall grade is golden-warm, the shadows deep brown rather than pure black, and the surfaces textured with materials that diffuse the warm light softly.

This compresses beautifully. Natural warm color gradients across organic materials — the exact scenario JPEG was designed for. An interior scene from the Hail Mary spacecraft compresses to roughly the same file size as a well-lit indoor portrait or a hotel room photo: modest-sized JPEG or WebP, clear and clean.

The contrast with the space exterior sequences is stark. The same streaming bitrate that handles an interior scene cleanly will struggle badly with a Rocky encounter scene, because the per-frame bitrate allocation across the video stream isn't matched to scene content. Streaming video uses variable bitrate (VBR), so complex frames get more bits than simple ones — but the complexity model used for allocating bits was optimized for photographic content, not for radial-glow VFX. Rocky's bioluminescence is genuinely a difficult case for rate-distortion optimization.

The Screenshot Problem and How to Actually Solve It

Screenshots from streaming services create a compression chain that makes things worse before you share them:

1. Streaming encodes the video as H.264 or HEVC/AV1. The original film negative was 8K or larger; what's being streamed is a compressed version.
2. Your screenshot tool captures a frame and saves it. On most platforms, the default is JPEG, which immediately applies a second round of lossy compression to an already-compressed source.
3. You share the screenshot. WhatsApp, Instagram, and Twitter all apply their own lossy JPEG compression to any image you upload.

By the time a screenshot of Rocky reaches someone's phone, it's been through three or four generations of lossy compression. Each generation amplifies the artifacts from the previous one.

The fix:

On iOS: Go to Settings → Photos → Transfer to Mac or PC → Keep Originals. iOS screenshots save as PNG by default on current iOS versions. Open in Optimage, export as WebP at quality 80.

On Android: Screenshots save as PNG by default on most modern Android builds. Same workflow: compress to WebP before sharing.

On desktop (Windows/Mac): Default screenshot tools save as PNG. Don't convert to JPEG at any point. Open the PNG in Optimage, export as WebP at quality 80-82.

For space sequences specifically (Rocky scenes, any exterior shots), set WebP quality to 82-85 rather than the standard 80 — the radial glow patterns need the extra quality budget to avoid the same ringing artifacts that JPEG introduces.

The One Exception: Pure Black Backgrounds

One of Project Hail Mary's visual signatures is frames where Rocky is the only light source and the background is genuinely pure black — not dark gray, not dark blue, but flat zero-value black across the entire background. These frames compress extremely well in WebP because of how WebP handles large uniform regions: zero-value pixels are encoded trivially, and the codec can allocate essentially its entire bit budget to Rocky itself.

In JPEG, even pure black backgrounds cause problems: JPEG's DCT encoding introduces a faint but measurable "ringing" around bright objects even when the background is meant to be empty black. WebP doesn't have this problem — its prediction coding can state "this region is empty" and move on. So paradoxically, the frames with the most extreme contrast (pure black plus glowing alien) sometimes compress more efficiently in WebP than frames with a slight but non-zero amount of dark star-field detail.

If you're sharing Rocky screenshots and want a clean result, the cleaner the background, the better WebP will handle it. Frames where Rocky is the only thing in the shot will compress better than frames where Rocky is in front of the star field.

Related reading:

• Silo Season 3's Dark Scenes: Why Your Screenshots Look Terrible and How to Fix Them — same dark-scene compression problem, different visual context
• House of the Dragon Season 3 Screenshots: Darkness, Fire, and How to Capture Both — another streaming compression challenge with extreme contrast
• AVIF vs WebP vs JPEG 2026 Benchmark — format comparison with high-contrast test images