Six Million People Are Heading to New York Harbor Tomorrow. Here's the Photography Problem They're About to Walk Into.

Tomorrow, the United States Navy hosts Sail250 in New York Harbor — a gathering of 60 ships from 30 countries for the International Fleet Review, one of the centerpiece events of America's 250th anniversary. The ships range from historic tall sailing vessels to modern naval frigates. Up to six million people are expected along the waterfront from lower Manhattan to Staten Island.

Every one of those six million people will have a phone camera. Most of them will point it at white sails against a bright July sky. And most of the resulting photos are going to disappoint, for the same technical reasons that affect all photography of bright white objects in full sunlight — but in a more severe form than usual.

Why Tall Ships in Sunlight Break Phone Camera Metering

The fundamental problem with photographing white sails is the same one that makes Wimbledon so difficult to shoot, but the scale is worse. Wimbledon has white clothing against green grass — a high-contrast boundary, but both surfaces are roughly within the same order of magnitude of brightness. White sails in direct July sunlight against a hazy harbor sky are reflecting nearly as much light as the sky itself, while the ship's dark hull, the crowd on the waterfront, and the buildings behind you are several stops darker.

Your phone's metering algorithm averages the scene. It sees a bright sky and a dark foreground and lands on an exposure that tries to split the difference. What that exposure actually means in practice: the sails are blown out to featureless white, the dark hull loses shadow detail, and the crowd in front of you is slightly underexposed. Every scene element lands at the wrong brightness simultaneously.

The color channel problem is separate and compounds this. The chroma subsampling in JPEG — which reduces the color channel resolution to save file size — creates visible color fringing along the boundary between a blown-out white sail and the blue or white sky behind it. On a large print or even a full-screen phone display, this fringing looks like a thin purple or cyan halo outlining each sail. It's not a focus problem. It's a compression artifact.

The Water Reflection Problem You Probably Haven't Thought About

Most of the discussion about maritime photography focuses on the sky and the ship. The water is an afterthought — but it's the most compression-hostile element in the frame.

Harbor water in direct sunlight is covered in sun glints: thousands of individual specular reflections of the sun that appear as bright points scattered across the surface. Each one is a tiny, high-frequency edge — a rapid transition from the dark or mid-gray water to a near-white bright point, then back. From a compression perspective, this is similar to a very fine grain structure, except the glints are arranged semi-randomly across a large portion of the image.

JPEG handles this by spending a disproportionate amount of compression budget on the water area. If you're compressing at JPEG quality 80, the codec is allocating its bit budget partly to the elaborate high-frequency content of the glinted water surface. The result: even if you nail the exposure for the sails, the water in the foreground is either compressed too aggressively (visible block artifacts) or the overall file is larger than expected because the codec is spending bits on the water.

WebP handles water significantly better than JPEG for the same reason it handles grass and noise better: its directional prediction and in-loop deblocking filter can encode the semi-regular pattern of sun glints more efficiently than JPEG's block-based DCT. A harbor scene in WebP at quality 80 will be smaller and look better in the water areas than JPEG at equivalent quality.

What to Actually Do on July 4

Tap on the ship's hull or the foreground crowd, not the sky. Setting exposure on a midtone reference prevents the camera from over-protecting the bright sky at the expense of the sails. The sails may still be slightly bright, but they'll have texture rather than being blank white.

Use 1x zoom, not 2x. Zooming in on the ships looks like a good idea from the waterfront, but at 2x your phone's camera is using a smaller aperture or cropping a larger sensor, which means less light per pixel and higher noise in the dark hull areas. The 1x lens captures more of the scene and gives you a cleaner source file to crop later.

Turn on HDR or night mode, even in daylight. Modern HDR modes take two or more exposures and merge them to recover highlight and shadow detail simultaneously. For a high-contrast harbor scene, HDR is worth the slight processing delay.

Shoot ProRAW or DNG if your phone supports it. The blown-out sail detail that looks gone in a JPEG preview is often actually present in the raw sensor data. ProRAW/DNG preserves it; you can pull back the highlights in Lightroom or Apple Photos afterward.

Don't share from the waterfront. New York Harbor on July 4 will have approximately six million people attempting to use the same cell towers. Large file transfers will be deprioritized, throttled, or fail entirely. Take your photos, enjoy the event, and share a compressed set from Wi-Fi when you're home.

The Format Question for Maritime Photography

JPEG has one specific failure mode that appears in every waterfront shot: the color fringing problem at sail edges. JPEG's chroma subsampling reduces color channel resolution to 4:2:0 (half the luma resolution in both dimensions). At the boundary between a white sail and blue sky, this means the color information — the blue that belongs to the sky — bleeds slightly into the sail area, and vice versa. This creates a faint but visible color halo.

WebP at 4:2:0 chroma subsampling (the default) has the same theoretical limitation, but its actual fringing is significantly less visible because the in-loop filter and prediction coding handle the sail-sky boundary more gracefully than JPEG's block-independent DCT. In practice: the same fringing problem exists in both formats but is visible in JPEG and not visible in WebP at equivalent quality settings and file sizes.

For harbor photography specifically:

• JPEG Q85: 1.5-3MB per photo, visible color fringing on sail edges, moderate block artifacts in water
• WebP Q80: 600KB-1.3MB per photo, no visible sail-edge fringing, water renders significantly cleaner
• AVIF Q68: 300-700KB per photo, best quality, slowest encoding, worth it for your best shots

The Sail250 event is a once-in-a-generation spectacle. The ships will look better in your photos than default phone JPEG output will suggest — and with a simple format choice before sharing, you can get images that actually reflect what you were standing in front of.

Related reading:

• Two Days Until America's 250th Birthday: Why Fireworks Photos Always Look Worse After Sharing — the night photography companion to today's daytime guide
• Wimbledon Day 3: The White-Kit Exposure and Compression Problem — the same white-on-bright-background challenge
• What Is EXIF Metadata and Why Strip It — your harbor photos know where you were standing