Two Days Until America's 250th Birthday. Here's Why Fireworks Photos Always Look Worse After You Share Them.

July 4, 2026 is the United States' 250th anniversary of independence — America 250 — and the fireworks shows being planned are larger than anything in recent memory. New York's Macy's show is expected to be the largest since at least 2000. San Diego's Big Bay Boom is launching from four barge positions simultaneously across the bay. Cities across the country that have had modest celebrations in recent years are going all-in for the 250th.

Millions of people will photograph those shows. Most of the resulting photos will look significantly worse than what was experienced in person — not because anyone took a bad photo, but because fireworks are one of the most technically hostile subjects for phone cameras and consumer image formats alike.

Here is what is actually happening, and what you can do about it before Friday night.

Why Fireworks Break JPEG

JPEG was designed in 1992 to compress the types of images most commonly encountered in that era: photographs of faces, landscapes, and scenes with natural color gradients and organic textures. It does this by dividing images into 8×8 pixel blocks and encoding each block as a sum of cosine waves — a mathematical representation that captures broad color patterns efficiently but struggles with sharp, high-frequency transitions.

Fireworks are almost entirely made of things JPEG handles badly.

Radial burst arms. The exploding star pattern of a fireworks burst creates dozens of thin, bright lines radiating from a center point. Each line is a high-frequency edge — a sharp transition from bright to dark that crosses multiple 8×8 JPEG blocks at an angle. JPEG can't represent those angled edges cleanly at its compression block size; it approximates them, producing ringing artifacts (blocky halos) along each arm of the burst.

Point-light-source intensity against black. Fireworks are bright objects against very dark sky. The extreme contrast at the edge between burst and darkness is exactly the kind of discontinuity that triggers JPEG's worst behavior — the same Gibbs-phenomenon ringing we wrote about in the Wimbledon white-kit post. But fireworks have this problem multiplied across every burst arm simultaneously, at multiple scales (the thick central trunk and the fine outer tendrils), in multiple color channels.

Color fringing in saturation transitions. Fireworks use chemical colorants — strontium for red, barium for green, copper for blue — that produce highly saturated colors. JPEG's chroma subsampling (which reduces color resolution to save space) introduces color fringing at the boundary between a saturated burst and the surrounding dark sky, particularly visible as a colored halo around each burst arm.

The High-ISO Problem on Top of That

Before we even get to the compression issue, phone cameras shooting fireworks on auto have an exposure problem. The scene is predominantly very dark — the night sky occupies most of the frame — and the camera meters for the overall scene average. It sees a dark scene and raises the ISO dramatically, often to 3200 or higher. At ISO 3200, the sensor's own noise floor introduces grain across the image, including in the dark sky areas between bursts.

The result is a photo where the dark areas between bursts are not a clean black, but a field of visible grain. When this is then JPEG-compressed, the codec has to spend bits on that grain (because it looks like real high-frequency image content), which means it has fewer bits left for the actual bursts. The bursts get compressed more aggressively, introducing more block artifacts. Everything degrades in parallel.

Why AVIF Is Actually the Right Format Here

AVIF was developed by the Alliance for Open Media and uses a fundamentally different compression technique than JPEG. Where JPEG uses 8×8 discrete cosine transform blocks, AVIF uses AV1's transform blocks — which can vary from 4×4 to 64×64 pixels and are chosen adaptively based on image content. For fireworks:

• Large uniform dark sky areas: encoded with large blocks efficiently
• Burst centers and arm structures: encoded with small blocks for precision
• The radial arm patterns: handled with directional prediction rather than cosine approximation

The result is that AVIF preserves the sharp geometry of fireworks bursts — the way the arms taper from bright center to fine trailing end — without the block artifacts or color fringing that JPEG introduces. At equivalent visual quality, AVIF files are typically 40-60% smaller than JPEG for fireworks images.

Format	Typical size for a good fireworks shot	Burst arm sharpness	Color fringing
JPEG Q80	1.2-2.5MB	Visible ringing	Noticeable
JPEG Q95	3-5MB	Greatly reduced	Reduced
WebP Q80	650KB-1.3MB	Minor ringing	Minimal
AVIF Q68	300-600KB	Very clean	None visible
PNG	8-20MB	Perfect	None

For sharing on social media, WebP at quality 80 is the practical choice — good quality, faster to encode than AVIF, and well-supported. For archiving your best shots, AVIF or PNG gives you a clean source to work from later. JPEG is the worst option available and the one most people default to.

What to Actually Do Differently on Friday

Before you go out: Switch your phone's camera app to night mode or pro mode. If using pro mode, set ISO to 200 and shutter speed to 1-3 seconds. If you don't have pro mode, look for a Fireworks scene mode — modern phones from Apple, Samsung, and Google added these after multiple iOS and Android releases brought them to broad availability.

Find a stable surface or bring a small tripod. Long-exposure fireworks shots require stillness — even a railing, a car roof, or sitting the phone on the ground pointing up works better than handholding.

After you've taken the shots: Don't share directly from your camera roll. The native camera app sends the original JPEG or HEIC file when you tap share, and WhatsApp will compress it aggressively, adding a second pass of lossy compression to an already-imperfect source.

Open the best 3-5 shots in Optimage, export as WebP at quality 80 (or AVIF at quality 68 if you want the best possible quality), and share those files. The file will be smaller than your phone's original and significantly smaller than a WhatsApp-compressed version — but it will look noticeably better because you controlled the compression pass instead of letting the app do it at the worst possible quality.

If you shoot long exposure: Long exposure fireworks shots — where multiple bursts stack into a single frame over a 2-4 second exposure — produce images with more complex content than single-burst shots, and they compress more efficiently. The burst trails are drawn-out streaks across the frame rather than single-point explosions, and the resulting image has a painterly quality that has less of the high-frequency edge problem. These shots are more forgiving on compression. WebP at quality 75 is fine for long exposures; they're still better than JPEG at equivalent quality.

America's 250th birthday fireworks will be spectacular by any historical measure. The photos are worth keeping — which means compressing them in a format that doesn't turn the burst arms into blocky approximations of themselves. Two extra steps between the shoot and the share is a reasonable investment for images this significant.

Related reading:

• Compress Images Without Losing Quality — the foundational guide to quality-controlled compression
• What Is EXIF Metadata and Why Strip It — your fireworks photos know where you were standing
• AVIF vs WebP vs JPEG 2026 Benchmark — format comparison with real data on high-contrast image content