OIM OBJECT INTERACTIVE MEDIA

It’s a PNG. And it carries its text inside.

With Object Interactive Media (OIM), digital media evolves into spatial and dynamic objects inside an ordinary image. It packs living layers, typography, and interactive logic into the same file, keeping an intact base image that any viewer can open.

PNG ANY VIEWER
ECDSA SIGNED AUTHORSHIP
57 KB THE PLAYER
Base PNG · any viewer
Live layers · OIM player
ES 1 file · 10 languages · signed
01 / 08

Generating is cheap. Maintaining isn't.

AI gives you a thousand versions in minutes. None of them can be edited, translated or indexed afterwards: the text was fused into the pixels.

Traditional Flow Redundant (5x)
showcase_es.png 66.6 KB
ES
showcase_en.png 66.4 KB
EN
showcase_zh.png 68.2 KB
ZH
showcase_fr.png 66.5 KB
FR
…showcase_de.png (67.1 KB) and more
DE
Total Storage 334.8 KB

Each translation requires re-exporting and storing a full PNG file with the text burned into the pixels (5 files = 334.8 KB).

OIM Flow (.oim.png) Efficient (1x) • -58%
chunk tEXt (OIM_Data)
{ "es": "Esto es OIM" }
Simulate language injection:
Total Storage 140.8 KB -58%

The tEXt chunk (OIM_Data) takes only 2.1 KB. A single 140.8 KB file serves all 5 languages without duplicating downloads or storage.

Global by design
A single .oim.png file serves the whole world. Changing or translating text is immediate, without re-exporting the base image.
Untouchable Quality
Re-exporting degrades or duplicates assets. OIM preserves the original IDAT bytes and injects the living layer into a signed tEXt chunk.
Real Interactivity
Traditional image formats lack DOM nodes and interaction events. OIM composes dynamic layers directly over the canvas at 60 FPS.
02 / 08

Interactive Comparison

Dynamic layers over the baked image. At first glance it looks like a standard PNG, but interacting with it reveals an overlaid metadata layer. This architecture allows serving multiple languages, animations, and interactive components from a single file, without touching base pixels or degrading quality. Drag the divider to compare the static image with its interactive layer.

▲ REVEALS BASE PNG
REVEALS OIM LAYER ▼
OIM interactive canvas with embedded translation and vector interactive layers
▲ HIDES OIM LAYER
HIDES BASE PNG ▼
03 / 08

3-layer separation

Because the text travels as text and not as pixels, search engines read it: your interactive images are indexable.

LAYER +1: DYNAMIC
What stays live
Text in every language, buttons, animations and, if you choose, filters and masks. The player draws it on top.
LAYER 0: SEPARATOR
The line between them
Symbolic: it holds nothing. It marks what becomes pixels and what stays live.
LAYER −1: BAKED
What you fix in the image
You choose which layers are baked into the PNG, filters and masks included. Any viewer shows it.
Baked
STATIC
Separator
Dynamic
// chunk tEXt: OIM_Data
{
"id": "offer-1",
"content": {
"es": "Hola OIM"
}
}
The HTML5 player assembles layers dynamically on the client device.
Zero additional GPU load; text is vectorized and responsive.
04 / 08

Use Cases

Explore OIM/OVM interactivity in action across different formats and workflows.

05 / 08

OIM Labs

The format, measured against the web that already exists. Reproducible tests, with open code and data.

06 / 08

OIM Ecosystem

The end-to-end suite for interactive media. Choose your starting point: every tool, every connector, every format.

Professional production, end to end

Visually design, add real-time multilingual layers, and distribute interactive media in a single file.

07 / 08

Stack & Integrations

Built on open standards and designed to fit any modern distribution workflow.

Core / Binary

TypeScript, Zod validation schemas, and raw Deflate compression (RFC 1951) packaged in PNG tEXt chunks.

TypeScript Zod Deflate

Web Component

A native browser element written in Vanilla JS. Zero external dependencies and direct DOM rendering at 60FPS.

Custom Elements Shadow DOM 60 FPS

Player Compatibility & Ad-Tech

Designed to be injected as an interactive layer on top of any HTML5 player and interactive advertising standards.

Video.js Plugin
VAST / VPAID Ad-Tech
Shopify Headless
React / Next.js / Vite
:::::: COMPRESSION // DEFLATE_RAW [wbits=-15]
[ SECURE // ECDSA_SHA256 ]
Cryptographic signature verification board ensuring visual content authenticity in OIM Ecosystem
08 / 08

Security and Trust

Security in OIM is designed to protect the intellectual property of your content. The baked image and its dynamic layer travel together as a single sealed piece, with no intermediary servers or trackers.

ECDSA Signature
Every export is sealed with a cryptographic signature. If anyone tampers with texts, translations or interactivity, the signature breaks and the viewer flags it.
Data embedded in the PNG
No intermediary databases: the dynamic layer travels compressed (raw Deflate) inside the file itself, alongside the baked image, shrinking the attack surface.
100% local rendering
Decompression and rendering happen in each user's browser. No third-party libraries, no ad trackers: privacy by default.
Contact

Any integration questions?

Try the OIM standard in your own infrastructure or let's discuss custom Enterprise support for your business.

Open-Core & Cloud Plans

The core format and players (@oim-media/core and <oim-player>) are open source under Apache-2.0. Cloud plans power OIM Studio, ECDSA signing, AI translation, and the Compiler API.

Free

Open standard under Apache-2.0 plus a free tier in OIM Studio.

Open standard
$0 /mo
  • 100 signed exports / mo
  • 100 MB storage
  • ECDSA signature for origin and integrity
  • Apache-2.0 @oim-media/core & <oim-player>
  • Official Penpot plugin & Web Viewer
  • No AI translation quota

Pro

For design and product teams shipping multilingual media at scale.

Early access
$29 /mo

Everything in Free, plus:

  • 5,000 signed exports / mo
  • 5 GB storage
  • 100 AI requests / day
  • Publish & embed on embed.oim.media
  • Cloud projects & version history in OIM Studio
  • Priority access to upcoming Figma & Framer plugins

Enterprise

For high-volume localization, API automation, and dedicated signing.

Volume & SLA
Custom

Everything in Pro, plus:

  • Unlimited signed exports
  • 50 GB storage
  • 1,000 AI requests / day
  • API keys for CI/CD & Compiler API
  • Dedicated ECDSA signing & custom retention
  • Service Level Agreement (SLA) & direct support

Custom quotas, DPA, and annual invoicing available under contract.

FAQ Common Questions

Everything you need to know about OIM

Clear answers on format architecture, licensing, web integration, and cryptographic security.

01 What is the OIM format and how does it work?

OIM (Object Interactive Media) is an open rich media format that decouples the rasterized base image from its interactive and textual layer. Everything is stored inside a standard .oim.png file via the tEXt chunk using raw Deflate compression.

When loaded with <oim-player>, the player parses the metadata in milliseconds and mounts an interactive layer over the DOM: text remains selectable, translatable, and accessible, while the background maintains full visual fidelity.

02 How does it differ from SVG, PNG, or Lottie?

Traditional PNG: Bakes text straight into pixels. Translating a banner requires opening design software and re-exporting multiple asset duplicates.

SVG: Great for simple vector iconography, but heavy and inefficient for high-resolution photorealistic textures or multi-layered photography.

Lottie: Superb for JSON vector animations, but lacks a raster-first paradigm with cryptographic authorship and decoupled runtime translation.

OIM merges the best of all worlds: universal PNG fallback compatibility with modern DOM interactivity, accessibility, and zero-overhead localization.

03 How does language injection work without duplicating assets?

A single .oim.png file holds text dictionaries for all configured languages. In your markup, simply define the lang attribute on the component (e.g. <oim-player lang="en">) or let it auto-detect user browser preferences.

The player swaps text nodes on the DOM instantly without secondary network fetches or re-downloading background assets, slashing CDN bandwidth by up to 85%.

04 What browsers and platforms support <oim-player>?

<oim-player> is a standards-compliant W3C Web Component (Custom Elements and Shadow DOM). It works out of the box on:

• Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge (modern desktop & mobile).
• Any modern web framework: React, Next.js, Vue, Nuxt, Svelte, Astro, or plain HTML.
• If JavaScript is disabled or a social crawler previews the link, the file gracefully renders as a standard PNG fallback image.

05 What is ECDSA cryptographic signing and immutable lock?

Every OIM file can be digitally signed using ECDSA (curve secp256k1), binding author identity to the SHA-256 hash of both layers and base image data.

Immutable Lock allows creators to seal their design: any unauthorized alteration of text, fonts, or pixels breaks cryptographic validity, guaranteeing asset provenance and integrity across enterprise workflows.

06 Is OIM open source or proprietary?

The ecosystem is architected for broad adoption and interoperability:

• Open Source (Apache-2.0): The binary format specification, the @oim-media/core parser library, and the @oim-media/player-oim web component are open source and free for commercial and community use.
• Proprietary: The OIM-Studio visual editor, Cloud integration extensions, backend signing APIs, and managed infrastructure are commercial services developed by Xue Studios LLC.

Let’s build a living standard
for image and video.

Object Interactive Media (OIM) is an open format, a metadata protocol, and a tooling ecosystem. Start today.