2D animated
Scenes built in layers so a change is a layer rather than a redraw, which is what makes a second language and a version two possible at all
an idea shown, not described
Explainer video production · UAE
The English version is for the buyer and the Arabic version is for the file, and a committee will expect one whether or not anyone plays it. Webzenia scripts both, in the same week.
Tell us what the product does, in your own wordsWhat the engagement produces
Three things come out of this work, and the animation is the last of them. The first two decide whether the second version is a version or an apology.
The one clear way to say what the product does, approved as words before anything moves. No animation rescues a script that does not make the point, and finding that out at the storyboard costs a conversation.
Which Arabic, decided alongside the English script rather than after it. Register and dialect are a commercial choice, not a preference, and the answer changes with who is watching.
A master in each language plus the shorter versions the funnel actually uses. A right-to-left caption changes the frame it sits in, so the second language is an edit rather than a track laid over the first.
What we make
Six ways to make an idea legible. Which one you need is decided by how abstract the thing is, not by how much motion you can afford.
Scenes built in layers so a change is a layer rather than a redraw, which is what makes a second language and a version two possible at all
an idea shown, not described
Type and shape doing the explaining, which is the format that survives a muted feed because the words are on screen rather than only in the voice
legible with the sound off
A process drawn as it is explained, which is the right register for a mechanism somebody has to follow rather than admire
a sequence a viewer can retrace
Numbers arriving in an order rather than all at once, so one figure is doing the work at a time
data a viewer reads rather than skips
The interface animated with callouts rather than filmed, so it can be corrected when the product changes instead of recorded again
a demo that survives a release
A character built as a turnaround rather than a drawing, so it stays on-model across every scene and every later video
a system, not an illustration
How an explainer gets made
A Dubai Internet City SaaS company selling into government-linked entities almost always arrives at the middle column first.
| A template animationBought as a style, filled with copy | English first, subtitled afterThe second language as a task | Scripted in both languagesTwo scripts, one production | |
|---|---|---|---|
| What you approve first | A style frame, before anybody has agreed what the video says. | An English script, which is the right thing done half way. | Both scripts, side by side, before a frame is animated. |
| The Arabic version | Not offered, and not really possible in the template. | A caption track sitting over a frame drawn for English. | Its own voice, its own timing, its own on-screen type. |
| In a committee file | It reads as something bought rather than made. | It reads as an afterthought, because it was one. | It reads as a document produced for the reader it went to. |
| When the product changes | You buy the template again. | You re-record, then re-time every caption. | You edit the layer and re-record one line in each language. |
| Who holds the project | The platform, and it expires with the subscription. | The studio, usually. | You do, with the scenes as layers and both scripts. |
Subtitling afterwards looks like the sensible half-measure, and it is the one that costs most. A caption track solves the file requirement and fails the viewer, because it sits outside a frame that was composed for a different reading direction, and it disappears the moment somebody watches with captions off. Doing it properly later means re-recording and re-timing everything, which is the second production nobody budgeted. Where the thing being explained is a real object that can be filmed rather than animated, that is product video production.
The UAE context
Webzenia has worked with Gulf clients since 2018. Four things decide whether an explainer works in this market, and the animation is not one of them.
A committee, a tender pack or a government-linked reviewer will expect an Arabic version whether or not anyone plays it. Treating it as a deliverable rather than a task is what stops it arriving as a caption track laid over a frame drawn for English.
Standard Arabic for formal, informative and pan-Arab content, including anything going into a file. Gulf dialect for a UAE-resident consumer audience, where the standard register reads as a news bulletin. An ADGM-registered fintech in Abu Dhabi needs the first; a consumer app usually needs the second.
They already know what category you are in and are checking whether you can explain yourselves. That changes the opening: the hook that suits a cold feed wastes the first ten seconds of a video somebody was told to watch, and the claim they are checking should arrive before the story does.
Promotional publishing here is permitted, and the permit covers promotion whether money changed hands or not. A line in a caption can be edited in an afternoon; the same line in two recorded voiceovers cannot. So the claims are checked before the recording, not after the file is in a submission.
What the engagement covers
Six parts, and the first three happen in words and drawings. Nothing is animated until the thing it says has been agreed.
We find the single claim the video exists to make, and write it down before anything else. A video trying to land four points lands none, and the discipline is subtraction rather than production.
Every scene drawn and timed against the script, so the runtime is a decision rather than a discovery. A board that runs long on paper runs long in the edit, and it is far less painful to cut here.
Which register the Arabic uses is settled in writing and signed off, then both languages are recorded and mixed to one loudness so neither version sounds like the quieter afterthought.
Scenes built in layers against the board that was signed off, which is what makes a later change a layer edit rather than a rebuild of the sequence around it.
The second language composed as its own edit, with the type set for the direction it reads in, then the shorter versions each destination needs derived from both masters.
Both masters, the caption files, both scripts and the project with its layers intact, in your name. Version two of an explainer is nearly always an edit, provided somebody kept the layers.
Our stack
The kit behind a video that exists twice and is not two videos. Select one to see why it earns its place, and what we do with it that most do not.
The storyboard is the last place a change costs nothing but a conversation. Seeing every scene at once, with the script under each frame, is how a video gets shortened before anybody has animated the part that should have been cut.
We board both language versions side by side, so a scene that works in English and runs long in Arabic is caught on the board rather than in the mix. Arabic lines frequently run longer, and a board only in English hides that.
How the work runs
The order is set by what has to be agreed in words. Everything expensive happens after the part that costs almost nothing to change.
The English script and the Arabic one are written in the same week, not in sequence, and the register is settled and signed off while it is still a sentence in a document. The board follows, with each scene timed, so the runtime is agreed before anyone opens an animation tool.
Both voiceovers are recorded by people who speak the language and mixed to one loudness against each other. The animation is then built to the approved board in layers, which is what makes a later change a layer edit rather than a rebuild of the sequence around it.
The Arabic version is composed as its own edit rather than captioned over the English, then the shorter versions each destination needs come out of both masters. What leaves is both films, both scripts, the caption files and the project with its layers intact, in your name.
The Arabic is written and recorded in the same weeks as the English, with the layers handed over.
Our commitment
Explainers fail at the script, at the second language, and at the moment somebody asks for version two. These four are about that.
No machine-translated Arabic
Never machine-translated, never synthesised, and read aloud by somebody who would notice if a sentence sounded wrong. A version produced by a tool is detectable by the audience it was made for, which is the audience that matters.
Register decided before recording
Standard Arabic or Gulf dialect is a scoped decision with a recommendation attached, agreed before a voice is booked. Discovering it at the mix means paying for a recording twice, and it is the most avoidable cost on this page.
Every claim needs evidence
A claim in a voiceover is set in two recordings and reaches an audience under a permitted publishing regime. If a line cannot be traced to something you hold, it is reworded before recording rather than after a file is submitted.
Project files are yours
Both masters, both scripts, the caption files and the working project transfer at delivery. Version two of an explainer is almost always an edit rather than a new film, and only if somebody kept the scenes as separable layers.
Common questions
Keep exploring
Marks, a bilingual system, and the files your team can run.
A position your licence supports and a buyer can verify.
A mark drawn in both scripts, and made to be fabricated.
A deck built for the pocket of capital reading it.
The document a vendor registration checks before anyone reads it.
One master that sets decks in both directions.
A master set your own team can fill, in both scripts.
One permitted shoot, cut for every place it sells.
Shot to two marketplace specs, against the sellable pack.
Next step
Send the product and who has to understand it. We will come back with a script angle and the Arabic decision that goes with it.
Tell us what you need.