RecordHTML guides
DOOH video specs: dimensions, frame rates and codecs
There is no single DOOH video specification that covers every screen network. A roadside display, an indoor portrait panel and a wide-format installation can need different dimensions, durations and encoding. Request the actual placement brief before exporting. RecordHTML can render an HTML5 creative at exact screen sizes, including its 4416×1656 preset, but a preset is only a starting point. It is not certification for a network or a promise that the file is ready for every player.
Start with the network and the individual screen
Identify the operator, inventory, orientation and native content canvas. A network name alone may not identify one resolution. Ask whether a file is required per screen group and whether any safe areas, reserved overlays or content restrictions affect the composition. Confirm whether the content fills one surface or is mapped across a larger installation.
OUTFRONT directs advertisers to its Media Finder for current production specifications, searchable by address, unit or media name. JCDecaux provides individual technical-specification pages, including Liverpool Towers and Old Street Showcases. The retrieved JCDecaux page text did not expose codec or frame-rate values, so none are invented here. Get the current brief for the actual placement rather than copying a setting from another screen.
Match the native dimensions before choosing encoding
The 4416×1656 preset is useful when the placement requests that exact canvas. It is not interchangeable with 3840×2160 or a generic ultrawide video. Enter custom even-numbered dimensions when needed and verify that your account pixel limit permits them. Build the creative layout for that shape rather than stretching an unrelated landscape composition.
Record at the intended browser viewport to check the real text wrapping, artwork scale and animation positions. Use crop and output scaling only when those transformations are part of the delivery plan. Look closely at logos, legal copy and text near edges. A formally correct pixel count does not ensure that a message will be readable at the viewing distance.
Confirm the exact frame rate and slot duration
The frame rate may be a whole number or a fractional NTSC rate. RecordHTML supports video options including 29.97 and 59.94 fps; choose what the operator requests rather than rounding casually. Confirm the required duration separately, including whether the final frame needs to hold and whether transitions belong inside the supplied file.
Creative markers can identify the segment to retain, but they do not change the booking specification. The tool records real-time browser playback and encodes an exact frame count; it does not guarantee deterministic offline animation evaluation. Review the output for smooth motion and unexpected blank states, particularly if the source uses large WebGL effects or many assets.
Treat codec, bitrate, pixel format and audio separately
Select MP4 for H.264 output when that matches the brief. The 4416×1656 preset suggests 29.97 fps and 15 Mbps CBR. Those are application hints, not a universal screen-network requirement. Choose the requested bitrate mode and pixel format, and confirm whether sound is required, allowed or must be absent.
Do not substitute GIF for full-size 4416×1656 delivery: GIF output is limited to 2,073,600 pixels per frame and whole-number frame rates up to 30. If the operator requires a container, codec or workflow that the application does not provide, arrange approved post-processing or use another delivery pipeline. RecordHTML does not currently export MOV.
Validate with the operator before the campaign
Make a checklist with native width and height, duration, frame rate, codec, bitrate, pixel format, audio policy, measured file size and naming requirements. Note which fields come from the operator and which are internal production choices. Check the downloaded file rather than relying on the settings you intended to submit.
Send a test asset early enough for the network to validate playback. Visual review should include the first and last frame, safe areas, legibility, motion and color appearance. Keep the exact source and settings used for the approved version. Public network guidance is useful context, but only the operator can confirm acceptance for the booked inventory.
Sources and scope
Checked October 22, 2026. Destination specifications and third-party tools can change. Follow the linked documentation and your actual placement brief rather than treating this guide as network approval.