Beyond the GIF: Creating Impact for Motion Creative Without Video Files

There is a tension at the heart of most animated display campaigns. The creative team wants motion that feels considered and polished. The media plan demands assets that pass platform validation and traffic without issue. More often than not, the solution is a compromise: a looping GIF that looks flat on a retina screen, or a video file that blows the file size cap before a single frame of animation has been refined.

At Banner Squad, we resolved that tension a different way. Through our own code-driven motion capability, we build complex, high-quality animated creative inside self-contained HTML files. No video, no GIF, no compromise on file weight. The motion lives in the code itself.

The problem with video and GIF in display production

Video files are simply too heavy for most programmatic display placements. A platform like Google Ads caps most animated HTML5 units at 150KB, a constraint that rules out video as a delivery format entirely for standard display. GIFs are lighter, but they come with their own limitations: a restricted colour palette, crude motion quality by modern standards, and a file size that can still exceed platform limits on anything more ambitious than a simple two-frame transition.

The result is creative that has been dialled back to fit the constraints rather than built to make the most of them. Motion that could have been fluid becomes stiff. Transitions that could have felt considered become functional at best. The platform gets a compliant file. The campaign gets something forgettable.

What code-driven motion makes possible

The approach we have developed at Banner Squad treats motion as something to be written rather than rendered. Rather than producing a video or GIF and attempting to compress it into a usable file size, we build the animation directly in code, as part of the HTML5 banner file itself.

This means effects that would require render time and significant file overhead in a video workflow can run in real time inside a lightweight HTML package. Particle systems, shader-based visuals, generative ambient motion, kinetic typography with frame-accurate timing: all of it built directly into the file, with no external assets required.

The creative quality goes up. The file weight stays well within spec. The two things that usually trade off against each other stop doing so.

Why file size matters more than most briefs acknowledge

File size caps are easy to treat as a technicality, something the production team handles after the creative has been signed off. In practice, they shape what is possible at the brief stage, and ignoring them early tends to create problems late.

Google Ads limits most animated HTML5 display units to 150KB. Many DSPs and programmatic environments sit in a similar range, with some allowing up to 200 or 300KB depending on the placement. A video asset cannot get near those limits. A well-constructed HTML5 file with code-driven motion can, consistently, across a full size set.

This matters because it removes a common point of failure from the production process. Files pass validation on the first upload. Campaigns traffic on time. There is no late-stage scramble to strip back the creative to meet a spec that should have informed the build from the start. Our HTML5 banner validator is available for teams who want to review existing packages before upload, but with code-driven production the compliance is built in rather than retrofitted.

What this means for DOOH

If code-driven motion is useful in display, it becomes genuinely powerful in DOOH. The conditions are different: larger screens, longer dwell times, no click interaction, and an environment where the creative has to work harder to earn attention without any of the targeting precision that digital display allows.

Ambient and generative motion is particularly well suited to this context. A looping particle field tied to brand colour. A fluid transition between campaign messages with no visible repeat point. Kinetic typography that moves with enough subtlety to feel intentional rather than intrusive. These are effects that ask for a second look rather than demanding it, which is exactly what outdoor environments reward.

Because the file is self-contained HTML rather than a video asset, it is also lighter to deliver, simpler to update between campaign flights, and more consistent across the variety of screen environments a DOOH placement might involve. One well-constructed file travels further and performs more reliably than a video render that needs to be re-exported every time something changes.

The creative possibilities in practice

The range of what is achievable through code-driven motion is broader than most display briefs currently ask for, partly because most clients have not seen it presented as an option. To make it concrete, here is a representative set of what we can build inside a standard HTML5 file:

• Particle systems and generative fields — responsive to brand colour and motion principles, creating visual texture that feels alive rather than mechanical
• Shader-based visual effects — the kind of liquid, light-responsive, or distortion effects that would require a render pipeline in video production, running in real time in code
• Kinetic typography — with frame-accurate timing, easing control, and the ability to choreograph copy reveals across a multi-frame animation with precision
• Ambient motion loops — with no visible repeat point, sustaining visual interest across the full duration of a DOOH dwell time without feeling repetitive
• Smooth multi-layer transitions — maintaining visual hierarchy and brand legibility throughout, with none of the compression artefacts that appear when the same effect is attempted in a GIF

None of this requires a different brief process or a longer production timeline. It is part of how we approach animated display production, applied where it adds the most value to the campaign.

How this fits into a standard production brief

This is not a specialist service that sits outside the normal production workflow. Clients brief us as they would for any animated campaign: formats, sizes, platform, assets, timelines. The code-driven motion capability is part of how we build, not an add-on that needs to be specifically commissioned.

Where it changes things is at the creative conversation stage. If you are open to discussing what the motion could do, rather than defaulting to a looping animation that mimics what a GIF would have done, the outcomes tend to be noticeably better. That conversation is most useful before the brief is locked, which is worth bearing in mind when you are planning the project.

If you are new to working with us, our guide to how to brief a banner ad production studio covers what to include and when to send it.

If your next campaign deserves more than a looping GIF

The file size limits that used to constrain motion creative are no longer a reason to settle for less. If you have an upcoming campaign and want to see what code-driven motion could bring to it, get in touch. We are happy to talk through what is possible before the brief is written.