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.
Base PNG · any viewer
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.
Each translation requires re-exporting and storing a full PNG file with the text burned into the pixels (5 files = 334.8 KB).
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.
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.
3-layer separation
Because the text travels as text and not as pixels, search engines read it: your interactive images are indexable.
"content": {
"es": "Hola OIM"
}
Use Cases
Explore OIM/OVM interactivity in action across different formats and workflows.
Interactive product sheets with real-time translation and purchase hotspots.
Vector masks and dynamic shapes layered on top of the base image canvas.
Scalable vector formats with coordinate-based interactive hotspots.
Lottie vector animations rendered dynamically and synced with viewer events.
Subtle parallax effects and interactive physics-based animations.
Interactive videos with temporal layers, dynamic hotspots, and playback control.
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.
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.
Web Component
A native browser element written in Vanilla JS. Zero external dependencies and direct DOM rendering at 60FPS.
Player Compatibility & Ad-Tech
Designed to be injected as an interactive layer on top of any HTML5 player and interactive advertising standards.
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.
Any integration questions?
Try the OIM standard in your own infrastructure or let's discuss custom Enterprise support for your business.
What each plan includes
Current limits during the closed beta.
- 100 signed exports / mo
- 100 MB storage
- ECDSA signature for origin and integrity
- No AI
- 5,000 signed exports / mo
- 5 GB storage
- ECDSA signature for origin and integrity
- 100 AI requests / day
- Publish works for embedding
- Unlimited signed exports
- 50 GB storage
- ECDSA signature for origin and integrity
- 1,000 AI requests / day
- Publish works for embedding
- API keys for integrations
Everything you need to know about OIM
Clear answers on format architecture, licensing, web integration, and cryptographic security.
01
¿Qué es el formato OIM y cómo funciona?
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
¿En qué se diferencia de un SVG, PNG o archivo 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
¿Cómo funciona la inyección de idiomas sin duplicar archivos?
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
¿Qué navegadores y plataformas son compatibles con <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
¿Qué es la firma criptográfica ECDSA e 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
¿OIM es de código abierto o privativo?
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.