MP5 technology

Video built as code. The MP5 generates a unique Smart Video on each viewer’s device, in real time, with no server rendering.

One template, unlimited variations

Blings pioneered On-Demand Generation: the Smart Video is built on your customer’s device at the Moment of Open, not pre-made on a server. One patented MP5 template can generate a unique version for every viewer.

Several phones showing personalized birthday video frames addressed to different viewers by name.

Features

On-device generation

The MP5 builds the Smart Video on the viewer’s device, so nothing renders on a server.

Built as code

It plays like video but runs on code, so it carries the full flexibility of the web.

Real-time data

The MP5 pulls live data at the Moment of Open, so every change in your database shows up instantly.

Lightweight

At just 60kb, the MP5 loads fast and keeps your page performant.

For developers

Our SDK gives developers full control to build personalized, logic-driven Smart Video with MP5.

Link to Live Demo

Personalized video frame inviting the viewer to build their own burger with a twenty percent discount.

Video markup language

Think of it as HTML for video. The same idea that made the web flexible now applies to Smart Video: build it and change it on the front end, with room for any interaction you can design.

Hand holding a phone showing a personalized video that thanks the viewer for signing up.

Frequently asked questions

How is the data rendered in an MP5?

Blings does not render. The MP5 holds the design, logic, and animation of the Smart Video template. When a viewer opens the Smart Video Link, the data is applied and the Smart Video is generated on-device, in real time. This is On-Demand Generation: nothing is pre-built on a server, and each viewer’s version assembles at the Moment of Open.

Where does the customer data come from?

From your existing data source. Blings connects to your CRM or data platform (Braze, Salesforce, HubSpot, or a data feed) and reads the fields you map to the template. Those values populate the Smart Video at the moment it is generated. You control the source, and Blings reads only what you map.

Does the MP5 file contain my customer data?

No. The MP5 contains the template: design, scenes, logic, and the field references that decide where data lands. The actual values are applied on-device at the Moment of Open and are never written into the file or stored by Blings. This is the Zero-Knowledge Architecture: Blings never sees or stores your PII.

Is MP5 an actual video file?

MP5 is a new type of video: video built as code. A traditional video file (MP4) is a fixed, pre-generated recording, one file per viewer. An MP5 is built as code instead of baked as pixels, so it carries the design, logic, and data references needed to generate the video on-device at the Moment of Open. That is what lets a single MP5 produce a unique Smart Video for every viewer, adapt in real time, and stay lightweight, none of which a standard video file can do.

Technical note: how the merge tags work.

Think of a merge tag the way you already use one in email. In your template you place a reference:
Hi {{first_name}}, your {{plan_name}} renews on {{renewal_date}}.

The MP5 stores the references, not the values. At the Moment of Open, Blings reads first_name, plan_name, and renewal_date from your mapped data source and generates the scene on-device. Same template, a different Smart Video for every viewer.