DOOH preflight · pilot
One HTML5 creative, tested and delivered for every DOOH screen
Send the creative and each network’s spec sheet. You get back every video file, a preview of every screen size, each dynamic scenario recorded, and a report that checks every file against its brief. Run it yourself in the app, or have us do it: €149 per campaign during the pilot.
The pilot button opens an email with the brief’s five questions in it; we reply on working days, Central European Time. See what comes back
The brief: 5 s, 25 or 30 fps, video up to 15 MB. This network also takes HTML5, so the creative itself is test-played as well.
bauer-media-outdoor-sweden/1080x1920.mp4
1080×1920 · 25 fps · 125 frames · 5.000 s · H.264
- Pixel size
- Frame rate
- Frame count
- Length
- Under 15 MB
- H.264
- No audio
bauer-media-outdoor-sweden/1920x1080.mp4
1920×1080 · 25 fps · 125 frames · 5.000 s · H.264
- Pixel size
- Frame rate
- Frame count
- Length
- Under 15 MB
- H.264
- No audio
bauer-media-outdoor-sweden/1080x1920.jpg · report.html
Every network asks for a different file
Five networks in three neighbouring markets, and no two briefs are the same. Some take the HTML5 creative, others only video, and the file size limit runs from 5 to 25 MB. A file that misses one line is sent back, and lead times leave little room: Bauer Media Outdoor UK asks for dynamic content three weeks before the campaign starts.
| Network | Length | Screen sizes | Frame rate | Video file limit | HTML5 |
|---|---|---|---|---|---|
| Bauer Media Outdoor, Sweden | 5 s | 1080×1920, 1920×1080 | 25 or 30 fps | 15 MB | Accepted |
| JCDecaux, Sweden | 5 s | 1080×1920 | 25 fps | 15 MB | Accepted |
| Ocean Outdoor, Sweden | 5–10 s | 1080×1920, 1920×1080 | 25 fps | 5 MB | Video only |
| JCDecaux, Netherlands | 6 s | 1080×1920 | 25 fps | 5 MB | Accepted |
| JCDecaux, Finland | 10 s | 1080×1920, 1920×1080 | 30 fps | 25 MB | Video only |
As listed in BidTheatre’s DOOH specification directory on March 17, 2026. Examples only: we work from the brief the operator gives you.
What comes back
Not a metadata check on a finished MP4: RecordHTML plays the HTML5 creative itself in Chrome, records it, and measures what came out.
Every video file
One MP4 per screen size and network, recorded in Chrome at the screen’s pixel size, with the frame rate, length and frame count the brief names, and encoded to stay under its file size limit.
Screen-size previews
A still of every size, taken from the recording itself, for the reference screenshots operators ask for and for your client’s sign-off.
Every dynamic scenario
For a creative that changes with weather, time or location: each variation forced and recorded at each size, with a matrix that names the scenario, how it was forced and the file it produced.
A technical report
Each file measured after encoding and compared with its brief, line by line: pixel size, frame rate, frame count, length, file size, codec and audio. Plus what the page did while it played: dropped frames, script errors and requests that failed.
One delivery package
A ZIP with a folder per network, files named the same way throughout, and the report inside it: it opens in a browser, plays the files next to it and prints as a PDF.
A link for your client
The same report as a page: every video, the scenario matrix and each file’s checks. The link is off until you turn it on, and you can turn it off again.
Dynamic creatives, every scenario on record
A creative that follows the weather or the time of day has more than one face, and the operator wants to see each of them before the campaign starts. Give the query parameters that force a variation, and each one is recorded at each size, without waiting for a cold morning.
- A matrix of every scenario, the condition that triggers it and the file it produced
- The parameters that force each one, so the operator can repeat the test
- A reference still of each scenario at each screen size
An example matrix: four scenarios at two sizes are eight recordings
| Scenario | Forced with | 1080×1920 | 1920×1080 |
|---|---|---|---|
| Cold morning | ?temp=2&hour=8 | Recorded | Recorded |
| Cold evening | ?temp=2&hour=19 | Recorded | Recorded |
| Warm morning | ?temp=24&hour=8 | Recorded | Recorded |
| Warm evening | ?temp=24&hour=19 | Recorded | Recorded |
Played the way a Broadsign screen plays it
A Broadsign player calls BroadSignPlay() at the moment the ad copy appears on screen. A creative that waits for that call shows nothing in an ordinary browser, and one that ignores it may be halfway through its animation when the screen shows it.
With Broadsign playback on, the recording runs with a BroadSignObject defined and the call made once the page has loaded, so the video starts where playback starts on the screen. A creative that has no such function is named in the report. This is a simulation in current Chrome. Broadsign Control embeds its own Chromium, version 87 or later, so the operator’s test on a real player still decides.
// The player calls this when the ad copy appears on screen
function BroadSignPlay() {
timeline.play();
}
// An ordinary browser never calls it: start right away there
if (typeof BroadSignObject === 'undefined') BroadSignPlay();How the pilot works
- 01
Send the creative and the briefs
A link or a ZIP of the HTML5 creative, each network’s spec sheet, and how to force each dynamic scenario. The request email asks for exactly these.
- 02
We confirm the scope
You get the list of files we will deliver and the date, by email, before you pay. One campaign covers up to 12 files.
- 03
We record, measure and check
We set the campaign up in the app: every size and scenario is recorded, then each file is measured and compared with its brief.
- 04
You get the link and the package
The report as a link, and the videos, previews and report in one ZIP. If the report finds a problem in the creative, fix it and we record the set once more.
Or run it yourself
The pilot uses the same campaign tool every account has. Every account gets 10 credits a month for free, with no card.
- 01
Name the creative
Paste its address or upload the ZIP, and switch Broadsign playback on if the screens run it.
- 02
Add the screens
Pick a network to start from its listed sizes, or type what the operator’s brief says: size, frame rate, length and file size limit.
- 03
Add the scenarios
For a dynamic creative, name each variation and the query parameters that force it. Leave it empty for a creative with one face.
- 04
Send the link
Every file is recorded and checked. Turn the client link on, or download the ZIP.
Who it is for
- DOOH production studios
- You build the creative and its variations, and every network on the plan wants its own file. The package is the part of the job that isn’t design.
- Programmatic DOOH agencies
- Your ad ops team traffics one campaign to several networks. Files that match each brief on the first upload keep the start date.
- Media owners
- Creatives arrive from agencies in every state. A recorded test and a measured report tell you what will play before it reaches a screen.
Pilot price
€149 per campaign
- One HTML5 creative
- Up to 12 delivered files: screen sizes × scenarios
- Previews, scenario matrix and technical report
- The delivery ZIP, a folder per network
- One new recording of the set after you fix the creative
Scope and date are confirmed by email first. You pay by card once they are agreed. Prices exclude VAT.
Questions
- Is this a certification for a network or a player?
- No. It is a test in current Chrome and a check of every file against the brief you send. Only the operator can accept a creative for its screens, and its own test on a real player is the last word.
- Which players do you simulate?
- Broadsign first: the recording runs with a
BroadSignObjectdefined andBroadSignPlay()called. Tell us if your screens run something else and what it expects from the page. - What if a network takes video only?
- Then the MP4 is the delivery. The same creative is recorded at that network’s size, length and frame rate, so HTML5 placements and video placements come from one source.
- Do you change my creative?
- No. We record what you send and report what we find. When the report shows a problem, you fix the creative and we record the set again, once per campaign.
- How is this different from the recorder?
- The recorder makes one file from the settings you enter; the DOOH video page and the specification checklist cover that. A campaign makes the whole set from one form: every size and scenario, each file measured against its brief, in one report and one package.
- What does the pilot add to doing it myself?
- Someone who does it for you: we read the briefs, set the campaign up, look at every recording and tell you what to fix, at €149 per campaign. The campaign tool is new, and the pilot is also how we learn which parts of this work matter most.
- What does it cost to run it myself?
- Credits, as for any recording: one per file up to 1920×1080 and 60 seconds, so a campaign of eight portrait and landscape files is eight credits. Every account gets 10 credits a month for free, with no card. A campaign holds up to 24 recordings; see pricing.
- Can I automate it?
- Single recordings, yes: the API takes the same settings as the record form, Broadsign playback included, so a list of screen sizes can become a batch of recordings from your own code. Campaigns are in the app only for now.
Sources
- BidTheatre: DOOH ad specifications: the network table above, as listed on March 17, 2026.
- Broadsign Control: HTML5 content: BroadSignPlay(), and the Chromium version the player embeds.
- Bauer Media Outdoor UK: dynamic campaigns: the three week lead time for dynamic content.
Have a DOOH campaign coming up?
Send the creative and the briefs. You get the scope and the date before you pay anything.