Colors remain accurate, contrast stays intact, all without asking the user to manually fiddle
For years, the promise of high dynamic range video has been undermined by a quiet inconsistency — the same image arriving differently on every screen, leaving viewers to wonder which version of reality the creator intended. With Android 17, Google introduces Eclipsa Video, a standard that works invisibly to reconcile what a display can show with what a filmmaker meant to convey. Built on a rare cross-industry collaboration between Google, Apple, and NBCUniversal, it represents a quiet but meaningful step toward a world where the medium no longer distorts the message.
- HDR video has long suffered a fragmentation problem — the same content looks washed out on one device and overblown on another, eroding the trust between creator and viewer.
- Subtitles fade, interface text becomes illegible, and users are left manually wrestling with brightness settings most never knew existed — a friction that Eclipsa Video is designed to eliminate entirely.
- By analyzing each display's luminance capabilities and recalibrating video frame by frame, Eclipsa Video automates what was once an expert-level workaround, restoring the image to the creator's original intent.
- Samsung's anticipated adoption through One UI 9 could extend this standard to hundreds of millions of Galaxy devices, transforming a Google-native feature into a potential industry baseline.
Google has built Eclipsa Video into Android 17 to address one of HDR's most persistent frustrations: the same video looking entirely different depending on the device playing it. A scene balanced on one phone might appear washed out on another, and text overlaid on HDR content often fades into illegibility as brightness shifts. The new standard resolves this automatically, analyzing a display's luminance in real time and recalibrating the video frame by frame — no user intervention required. Where Android 16 asked viewers to make these adjustments themselves, Eclipsa Video handles it invisibly, preserving color accuracy, contrast, and the creator's original intent.
The practical gains extend beyond picture quality. On-screen text, subtitles, and interface elements — long casualties of aggressive HDR brightness — remain readable without sacrificing the visual impact of the content itself. This kind of intelligent dynamic range management has been technically possible but rarely implemented at the system level.
Eclipsa Video is grounded in SMPTE ST 2094-50, a specification developed jointly by Google, Apple, and NBCUniversal — an unusually collaborative effort that signals genuine industry consensus around solving the HDR consistency problem. Samsung has already indicated plans to bring support to Galaxy devices via One UI 9, which would carry the standard well beyond Android's native ecosystem and into one of the world's most widely used device families.
The broader significance is a shift in philosophy: HDR playback moving from a feature that rewards technical users to one that simply works. For creators, it means their work survives the fragmented device landscape intact. For viewers, it means fewer compromises. The real measure of Eclipsa Video's success will come as streaming platforms and manufacturers integrate it into their pipelines — and as the gap between what a creator intended and what an audience sees continues to close.
Google has introduced Eclipsa Video, a new standard for high dynamic range playback built into Android 17, designed to solve a problem that has plagued HDR content for years: the same video looks wildly different depending on what device you're watching it on. A scene that appears perfectly balanced on one phone might look washed out on another, or the text overlaid on the video might become illegible as the brightness shifts.
Eclipsa Video addresses this by automatically adjusting HDR content in real time based on the brightness capabilities of whatever display is showing it. The system analyzes the screen's luminance and recalibrates the video frame by frame, ensuring that colors remain accurate, contrast stays intact, and the overall image quality stays true to what the creator intended—all without asking the user to manually fiddle with settings. On Android 16, viewers had to make these adjustments themselves, a tedious workaround that most people either didn't know about or simply ignored.
One of the more practical benefits is that on-screen text and interface elements no longer get swallowed by the brightness of HDR video. Anyone who has tried to read subtitles or menu options during an HDR film knows the frustration of watching them fade into illegibility. Eclipsa Video keeps these elements readable by managing the dynamic range more intelligently, preserving legibility without sacrificing the visual impact of the content itself.
The technology is built on the SMPTE ST 2094-50 standard, a technical specification developed collaboratively by Google, Apple, and NBCUniversal. This kind of cross-company cooperation on video standards is relatively rare and suggests that the industry sees real value in solving the HDR consistency problem. The standard provides a framework for how devices should interpret and display HDR metadata, creating a common language that manufacturers can build on.
Samsung has already signaled interest in bringing Eclipsa Video support to its Galaxy devices through the upcoming One UI 9 update, which would extend the technology beyond the Android ecosystem and into one of the world's largest smartphone manufacturers. If Samsung follows through, it would represent a significant step toward broader adoption of the standard and a practical benefit for millions of users who own Galaxy phones and tablets.
The rollout of Eclipsa Video marks a shift in how the industry approaches HDR playback—from a feature that requires user expertise to manage, to one that works invisibly in the background. For content creators, it means their work will look more consistent across the fragmented landscape of devices. For viewers, it means fewer compromises and less tinkering. The real test will come as the standard spreads beyond Android and Samsung, and as streaming services and device makers fully integrate it into their workflows.
Citas Notables
Unlike Android 16, where users had to manually adjust HDR brightness, Eclipsa Video runs these improvements automatically— Google (via Android 17 documentation)
La Conversación del Hearth Otra perspectiva de la historia
Why does the same HDR video look so different on different phones? Is it just a matter of screen quality?
Partly, yes—but the bigger issue is that HDR metadata doesn't automatically translate across devices. A TV might be capable of much brighter peak brightness than a phone, so the same video file needs to be interpreted differently on each one. Without adjustment, you get either washed-out images or illegible text.
So Eclipsa Video solves this by doing the adjustment automatically?
Exactly. It reads the display's capabilities and recalibrates the video frame by frame. The user doesn't have to do anything. On Android 16, you had to manually tweak brightness settings if you wanted it to look right.
That sounds like it would require a lot of processing power. Does it slow things down?
The standard is designed to be efficient, but I don't have specifics on performance impact. The real innovation is that it's frame-by-frame, not just a blanket adjustment. That precision is what keeps colors accurate and contrast intact.
Why did it take Google, Apple, and NBCUniversal working together to create this?
Because HDR is still relatively new, and there's no universal agreement on how to encode and display it. Having major players align on a single standard—SMPTE ST 2094-50—means manufacturers can build compatible devices without guessing.
And Samsung's interest suggests this could become the default way HDR works?
That's the hope. If Galaxy devices support it through One UI 9, and other manufacturers follow, then in a few years this might just be how HDR works, invisible to the user.