
Tools and providers
Part of Ad creative software: test versioning on your work
Ad creative software: test versioning on your work
Use a real campaign master to test how ad creative software handles sizes and copy variants, then time exports and count manual fixes.
What to take away
- Ad creative software earns its licence when one approved master must become dozens of live files across standard display sizes, not when a team needs three resizes.
- Test every candidate on the same specimenone master, one changed headline, a fixed set of sizes, a stopwatch.
- Resizing fixes geometry, not meaning. Legibility, claim wording and ad disclosure still need a person to sign off.
- Fix naming, source files and the approval route before you buy. Multi-size production usually fails at intake, not at export.
Why multi-size production fills the studio diary
A versioning tool holds a master and generates the sizes, ratios and copy variants a campaign needs. The work is mechanical: swap text, reposition crops, export, repeat. It exists because media plans land late and the same message has to run in many places on the same day.
Candidates range from template apps to studio suites. Canva's business plans are built for individuals and small teams, and Adobe Express is marketed as the quick and easy create-anything app. Studios with source files usually keep Adobe Photoshop or Figma in the chain for the master, then test the candidate's resize and bulk-export features on top.
IAB UK standard display units
Leaderboard
- Pixel size
- 728x90
- Placement
- Top of page
Medium rectangle
- Pixel size
- 300x250
- Placement
- In-content
Skyscraper
- Pixel size
- 160x600
- Placement
- Side column
British display buying leans on a small set of IAB UK standard units, including the 728x90 leaderboard, the 300x250 medium rectangle and the 160x600 skyscraper. One campaign can multiply those by several headlines, prices and calls to action, and then again by the differing limits of each media owner.
What a UK campaign usually has to cover
Most UK display plans mix standard units with platform-specific sizes, and every media owner sets its own file weight, animation and audio rules. A tool built for resizing alone will leave the awkward jobs to a person.
Each owner publishes its own limits. Google Ads and Meta both set size, file weight and animation rules for their display placements, and the standard units above do not override them. Pull the current spec sheet before you run the test, because a build that passes on one network can fail on another.
Production jobs a versioning tool must cover
- Size resizingreflow layout, keep hierarchy, one-pass export
- Copy versioningswap text fields without editing master
- Regional wordinghold separate copy set per variant
- Format conversionproduce HTML5 or animated build
- Withdrawalproduce dated record of what ran where
When a supplier promises HTML5 output, the checkable reference is the specification published by the W3C as the HTML 5.2 Recommendation.
| Production job | What triggers it | What the tool must do |
|---|---|---|
| Size resizing | A media owner joins the plan | Reflow the layout, keep the hierarchy, export in one pass |
| Copy versioning | A price, offer or headline changes | Swap text fields without editing the master |
| Regional wording | A campaign runs with different wording across the UK | Hold a separate copy set for each variant |
| Format conversion | A static master is needed as HTML5 or animated | Produce a build that meets the published specification |
| Withdrawal | A claim is pulled or the campaign ends | Produce a dated record of what ran where |
A specimen test that beats a sales demo
No demonstration matches one honest test on your own work. Run it in this order.
- Take one real master with its source file and licence record.
- List the exact sizes and copy variants from your last three campaigns.
- Change one headline and one price inside the tool, then export the full set.
- Time the run and count every manual fix needed after export.
- Ask a colleague who has never used the product to repeat step three.
Use the same specimen for each candidate so the timed run and manual-fix count are comparable.
Where versioning stops and judgement starts
Automated resizing preserves layout, not argument. A squeezed headline can shift what a claim means, and a resized price can lose the qualifying words beside it. The CAP code, administered by the ASA, requires ads to be legal, decent, honest and truthful and recognisable as marketing, so the advertising codes belong in the brief rather than in a final check.
If the tool writes copy or selects imagery from customer data, the ICO's guidance on artificial intelligence sets out what a lawful basis and a transparency notice look like. Versioning a claim is easy. Evidencing why you may use the data behind it is not.
The cost arithmetic, worked once
Assume a studio rate of £450 a day for a campaign needing 60 finished sizes; these are illustrative figures, not a market rate. Manual resizing at eight files an hour takes about seven and a half days, or roughly £3,375.
If a tool produced the set in a morning, the arithmetic would change. The licence is one line only: seat cost, onboarding, template build and checking time all count.
The saving depends on the state of the source files, so ad creative asset management and consistent naming come before any licence decision. If a master is a flattened JPEG, the tool inherits the mess.
Common questions
Does versioning software replace a studio team?
No. It removes repetition from resizing and copy swapping. Judgement about claims, brand and disclosure stays with people.
How many sizes should one master cover?
Start from your own evidence: count the sizes in your last three media plans. Buying for sizes you have never run is guesswork.
Is banner resizing software enough on its own?
For static display, often yes. Video, HTML5 builds and regulated claims usually need a fuller production route and a second pair of eyes.
What should we ask a supplier to prove?
Ask for the same specimen test, timed, on your master. A recorded export log and a named support route matter more than a feature list.



