News
Google’s Eclipsa Video targets calmer, more consistent HDR on Android 17
Google is introducing Eclipsa Video, an open HDR format designed to make mobile video look more consistent across phones, tablets and TVs running Android 17.
Google is introducing Eclipsa Video, a new HDR format designed to make video look more consistent across different screens. The technology is built into Android 17 and is aimed at a familiar mobile-video problem: a clip that looks balanced on one phone can appear painfully bright, flat or washed out on another display.
The announcement is particularly relevant to anyone who watches video through social feeds, messaging apps or streaming services. HDR is meant to preserve bright highlights, deep contrast and the creator’s intended look, but devices have different brightness capabilities and manufacturers do not always interpret HDR metadata in the same way. Google says Eclipsa Video is intended to give compatible displays clearer instructions for rendering the same content.
A shared rulebook for HDR playback
Eclipsa Video builds on the open SMPTE ST 2094-50 specification, which Google developed with Apple and NBCUniversal. Instead of leaving every screen to make its own assumptions, the format carries additional guidance about how the image should be displayed.
That guidance is designed around three ideas. First, Eclipsa Video establishes a consistent HDR reference white, giving standard text, interface elements and standard-range colours a more predictable brightness baseline. This matters on a smartphone, where a sudden burst of HDR brightness can make surrounding captions or controls uncomfortable to read.
Second, the format accounts for the headroom available on each screen. A premium television may be able to show much brighter highlights than a phone, while a smaller mobile display needs to scale those highlights more carefully. Eclipsa Video is designed to adapt the presentation without simply flattening the entire image.
Third, the format preserves creative intent through adaptive, frame-by-frame instructions. Those instructions can tell a compatible display how to handle changes in brightness, contrast and colour as the scene evolves. In practical terms, the goal is for a video to retain its visual character when it moves between a handset, a tablet and a living-room screen.
Android 17 brings native platform support
Google says Eclipsa Video support is built directly into Android 17 for phones, tablets and TVs. The company’s broader Android 17 announcement positions media and camera improvements as part of the platform update, while the dedicated Eclipsa Video briefing explains how the HDR format is expected to work.
Native platform support should reduce the amount of custom work required from individual apps. Google says Eclipsa Video playback and capture are supported on devices running Android 17, provided they have HDR displays that pass Eclipsa compliance tests. That qualification is important: Android 17 alone does not guarantee that every phone or television will support the feature in the same way.
Google also says the technology is rolling out and that more applications and devices will support it over time. The announcement does not provide a universal list of compatible handsets, televisions or streaming services, so users should treat current support as dependent on both the Android version and the hardware.
What changes for app developers
For developers, the most significant part of the announcement is the integration with Jetpack Media3. Google says ExoPlayer can handle Eclipsa Video metadata automatically through the updated media stack, without requiring additional player configuration. That could make it easier for video applications to adopt the format while keeping playback behaviour consistent across Android form factors.
Google is also publishing implementation guidance for capture and playback, alongside open-source tools that let developers inspect SMPTE ST 2094-50 metadata and dynamic gain curves. Its HDR Explorer is intended to help teams understand how the instructions are being interpreted in real time. This gives app makers a way to check their media pipeline before presenting Eclipsa Video content to users.
The format is therefore aimed at more than the display layer. A camera app needs to preserve the relevant metadata when recording or exporting a clip, while a social or messaging app needs to avoid stripping that information during upload, processing or playback. If any stage removes the metadata, the final image may no longer receive the display guidance that Eclipsa Video is designed to provide.
Why this matters on smartphones
Mobile video is increasingly consumed in mixed environments: a user may record on a phone, edit in an app, share through a social platform and later watch the same clip on a tablet or television. That workflow exposes differences between displays more often than traditional camera-to-TV playback did.
A more consistent HDR layer could make those transitions less distracting. It may also help creators avoid choosing between a vivid master that looks harsh on some phones and a conservative version that loses impact elsewhere. For viewers, the promised benefit is simpler: fewer unexpected brightness jumps and a more stable appearance when moving between screens.
Those are platform goals rather than independent test results. Google has announced the format and its Android 17 integration, but real-world consistency will depend on compliant displays, application support and the way services preserve Eclipsa metadata through their own processing pipelines.
Eclipsa Video is consequently best understood as infrastructure for the next phase of mobile video, not an instant visual upgrade for every Android device. As Android 17 reaches more hardware and developers begin integrating the format, its success will be measured by how reliably a clip keeps its intended look from the smallest phone display to the largest compatible screen.