In today’s fragmented media landscape, graphics have become more critical than ever. Lower-thirds, scorebugs, data-driven overlays, social callouts, and sponsorship graphics are no longer limited to traditional linear television. They now need to appear seamlessly across live broadcasts, OTT platforms, post-production edits, and even social media cutdowns. Yet, for many broadcasters and ISVs, delivering those assets consistently across platforms has been a headache.
That’s where OGraf, the new open graphics specification from the European Broadcasting Union (EBU), comes in.
Why OGraf Matters?
At its core, OGraf is built on a simple but transformative principle: create once, deploy everywhere. Instead of building one version of a graphic for live playout, another for a streaming pipeline, and yet another for post-production, OGraf standardizes how HTML-based graphics are:
- Created – defined as modular web components with a manifest file (.ograf.json) containing metadata.
- Controlled – using a common, expandable command interface (playAction(), goToTime(), etc.) across different systems.
- Played Out – rendered consistently by any OGraf-compliant system, whether it’s a broadcast engine, a cloud-based OTT service, or an editing timeline.
For broadcasters, this eliminates redundant work and reduces errors. For ISVs, it creates new opportunities to integrate graphics engines, controllers, and renderers without being locked into proprietary formats.
Interoperability: The End of Fragmentation
Historically, graphics workflows have been siloed. Editors, control systems, playout servers, and renderers often came from different vendors — and rarely played nicely together. OGraf tackles this problem by defining a vendor-agnostic data model that ensures compatibility across the production chain.
That means a sports broadcaster can design a scorebug once and know it will:
- Update in real time during a live match.
- Appear frame-accurate on OTT streams.
- Be dropped into a post-production highlight package without re-rendering.
The result is fewer bottlenecks, faster turnaround, and lower costs.
Flexibility: Real-Time and Non-Real-Time
OGraf isn’t limited to live television. Its specification supports both real-time graphics (for live overlays, tickers, and data feeds) and non-real-time graphics (for editing timelines, pre-rendered packages, and automated publishing).
Through its command interface, a controller can:
- Trigger a lower-third in live playout.
- Advance a graphic to a specific timestamp in a highlight reel.
- Manage resolution, framerate, and rendering environment requirements.
This dual capability makes OGraf equally valuable for broadcasters, streaming services, and post houses.
Adoption Without Disruption
Change is always a concern in broadcast workflows. The good news is that OGraf was designed with incremental adoption in mind:
- Existing HTML graphics can often be adapted by wrapping them in OGraf’s manifest and component structure.
- Early implementations from companies like SPX Graphics, Loopic, and Media Tailor show how OGraf can sit alongside existing systems without forcing a wholesale migration.
- The upcoming Server API will further streamline communication between controllers and renderers, opening the door for more advanced orchestration.
In other words: you don’t have to rip and replace. You can start small, test with one graphics pipeline, and expand as confidence grows.
What This Means for Broadcasters and ISVs
For broadcasters and streamers:
- Consistent branding across every output channel.
- Reduced costs and faster delivery.
- Fewer vendor lock-ins and more flexible partnerships.
For ISVs:
- A common foundation for building graphics solutions that integrate easily with other vendors’ tools.
- Faster adoption by broadcasters who no longer fear fragmentation.
- The ability to innovate on top of a trusted, open standard.
The Road Ahead
- Top five repeatable graphics packages identified, with data models
- Renderer and control pair available to test against draft v1
- CI/CD pipeline that can validate package structure and run regression tests
- SBOM and license scanning in place for all dependencies
- Rollback and fallback plan defined for live playout
- Metrics such as cycle time, failure rate, and documentation coverage in place to measure progress
The first draft of OGraf’s specification was released in April 2025, with Version 1 set for official release at IBC 2025. Momentum is building quickly: early adopters are already showcasing prototypes, and more vendors are signaling support.
OGraf represents more than just a technical spec — it’s a shift toward a modular, interoperable future in broadcast and streaming graphics. By standardizing the foundation, it frees creative and technical teams to focus on storytelling, monetization, and innovation.
Create once, deploy everywhere. That’s not just a slogan — with OGraf, it’s becoming a reality.
| Category | Details |
|---|---|
|
What It Is |
An open EBU specification for HTML-based broadcast graphics. |
|
Core Value |
Create once, deploy everywhere — the same graphic works across live TV, streaming, and post-production. |
|
Key Features |
Modular Web Components with manifest file (.ograf.json); Vendor-agnostic data model; Expandable command interface (playAction(), goToTime()); Works in both real-time and non-real-time workflows
|
|
For Broadcasters |
Consistent branding across platforms; Faster delivery, lower costs; Freedom from vendor lock-in
|
|
For ISVs |
Easier integrations with broadcaster systems; Faster adoption of graphics tools; Opportunity to innovate on top of a shared standard
|
|
Status |
Draft spec released April 2025 Version 1 release planned for IBC 2025 |
|
Why It Matters |
Promotes interoperability, flexibility, and scalability across fragmented broadcast ecosystems. |
Bottom line: OGraf is for engineering and product teams, not for producers or viewers. But when ISVs, broadcasters, and streamers adopt it, everyone benefits: vendors gain speed and flexibility, while broadcasters and streamers deliver consistent, reliable graphics across every screen.
A Low-Risk Adoption Path with Xperity’s Synthesis Framework (XSF)
For organizations that want to move quickly without disrupting existing workflows, Xperity offers a structured path through the Xperity Synthesis Framework (XSF).
XSF combines AI-assisted development, pre-built frameworks, and proven engineering expertise to help organizations:
- Pilot OGraf adoption with a single graphics package Harden pipelines with validation, governance, and compliance gates
- Bridge legacy systems like CasparCG or SPX during the transition
- Codify templates and documentation so teams can scale adoption cleanly
Like to learn more about OGraf?
Contact Xperity to help you innovate today!
