Skip to main content

Getting Started with OGraf

OGraf is designed as a modular architecture for broadcast graphics. Instead of one closed system, OGraf defines a common interface so different tools can work together across the production chain.

Core Roles in the Workflow​

An OGraf workflow typically involves four main roles:

  • Editor – Tool where users visually design graphics and define fields to be controlled.
  • Controller – Software for managing graphics, controlling playout actions.
  • Server – Optional; provides APIs for managing and scheduling graphics.
  • Renderer – Executes the OGraf package and displays it, often in a browser or playout system.

Each component can come from a different vendor. The specification ensures they remain interoperable, making it possible to mix and match tools freely.

Built for Real-World Needs​

OGraf balances modularity with compatibility, allowing graphics to be reused in live broadcast, web, streaming, or post-production workflows. The use of HTML5, Web Components, and portable formats makes them flexible across platforms.

No-Code-Friendly, Modern Styling​

One of OGraf’s strengths is that it can be used without writing a single line of code. Instead of dealing with HTML, CSS, or JavaScript directly, creators can work in familiar design environments.

For example, StreamShapers Ferryman allows designers to build templates visually inside Adobe After Effects. From there, the tool automatically generates the required OGraf schema, manages assets, and exports a complete package, ready to be used in controllers and renderers.

This approach lowers the entry barrier for broadcasters, designers, and content creators: you can focus on layout and animation, while the technical parts of OGraf are handled in the background.