Do not treat video context as “more prompt.” Treat it as pre-production. The more you decide before rendering, the fewer credits you spend fixing avoidable script, voice, product, or pacing issues.
Start with the workflow
Pick the workflow before you attach files. Different video types need different context.What to provide
Script and storyboard
Hook, angle, scene order, voiceover, CTA, target length, and which moments must be shown rather than invented.
Product and UI references
Product shots, packaging, labels, app screenshots, website captures, screen recordings, demos, and any exact visual assets.
B-roll and source footage
Existing clips, customer footage, founder footage, testimonials, app walkthroughs, product handling, lifestyle clips, and old ads to reuse.
Reference videos
Examples of pacing, framing, creator delivery, edit density, caption style, hook structure, or visual mood.
Voice and pronunciation
Language, market, accent, age, gender, pace, tone, custom pronunciation, brand-name spelling, acronyms, and words that are often misread.
Claims and guardrails
Approved claims, forbidden claims, required disclaimers, testimonial rules, legal restrictions, and anything the ad must not imply.
Caption and overlay rules
Caption style, position, emphasis, on-screen text, subtitles, end card, offer text, CTA, and what should be edited after render.
Export requirements
Target platforms, aspect ratios, safe zones, duration, file handoff needs, and whether the output is for testing or final launch.
What belongs where
Some video information is durable. Some only belongs to one video.How context is used
Understand what stays in the current chat and what becomes durable context.
Saved video defaults
Use Context & Skills → Video Context for video defaults that should apply across future generations for the brand. These settings are saved at brand level and are passed to the video agent before it generates.Auto does not mean “ignore this setting.” It means Superscale makes the choice for the current video, and if it uses captions or an end card, it should use the saved brand style.
Use real footage when exactness matters
AI can generate useful motion and scenes, but it should not be asked to invent details that have to be commercially exact. Use real footage, screenshots, or product references for:- App UI, website flows, dashboards, checkout pages, and onboarding steps.
- Product packaging, labels, bottles, supplements, books, devices, and physical product shape.
- Founder, customer, testimonial, clinical, financial, legal, or regulated proof.
- Precise text, pricing, small UI labels, logos, disclaimers, and compliance language.
- Game footage, software walkthroughs, before/after proof, or any result that must be literal.
- Hook scenes, transitions, explainers, creator intros, visual metaphors, background lifestyle shots, and fast concept variations.
- Shots where mood and message matter more than exact product fidelity.
- Early exploration before you commit to a higher-control hybrid edit.
If a logo, product, UI, or text must not change, attach the exact source asset and say what must stay fixed. Do not rely on the video model to redraw exact commercial assets from memory.
Script and scene plan
Video context should tell Superscale what each scene is supposed to do. A good scene plan is short but explicit.Do not ask the video model to draw captions, subtitles, logo holds, or end-card frames inside the generated scene. In Superscale’s current video flow, captions and end cards are post-processing layers. Keep the generated video focused on the scene, then apply captions and the end card through the video settings or the final edit.
Voice and localization
Voice context is about market fit, not just language. Before rendering, specify:- Target market and language variant, not just the language.
- Accent and delivery: energetic, calm, founder-like, creator-style, premium, playful, technical, native, or studio.
- Pronunciation hints for brand names, product names, acronyms, payment terms, and unusual words.
- Whether the voice is native audio, voiceover, or a silent/ambient scene with captions.
- Whether visuals need localization too: currency, screenshots, people, examples, slang, competitors, and claims.
Captions, overlays, and end cards
Captions are part of the creative, not a finishing detail. Decide them before rendering when they affect pacing or safe zones. Use context to define:- Caption preset or style: subtle, bold creator captions, high-contrast, editorial, playful, or plain.
- Position: bottom, top, center, or safe-zone-specific.
- Shadow strength: none, light, medium, or heavy depending on how busy the footage is.
- Baseline and highlighted text: font, weight, color, and which words or phrases need emphasis.
- Overlay copy: headline, proof point, CTA, offer, discount, disclaimer, or app/store badge.
- End card: final screen, logo, product, URL, CTA, promo code, or app-store prompt.
Before spending video credits
Run this check before the first render.Lock the goal
Decide whether the video is a hook test, product demo, testimonial-style ad, localization, retargeting creative, or winner iteration.
Choose the workflow
Pick full AI, UGC speaking, UGC lifestyle, B-roll voiceover, animated, or Studio/hybrid before choosing assets.
Approve the script
Review hook, claims, spoken line, CTA, and target length before rendering. Fix script problems in chat, not after video generation.
Attach exact inputs
Add the product shot, UI screenshot, screen recording, B-roll, voice notes, reference ad, or testimonial that should guide the output.
Mark what cannot change
Say what must stay exact: product, label, logo, UI, price, claim, disclaimer, voice, caption, or source clip.
Check voice and market
Add language, accent, pronunciation, delivery style, and localization notes before a full batch.
Plan captions and end card
Decide caption style, overlay text, CTA, and final frame before export.
Common video context mistakes
Asking the model to invent exact product footage
Asking the model to invent exact product footage
If the product, UI, packaging, or claim must be accurate, attach the real asset. Use AI to create around the asset, not to guess it.
Treating B-roll as decoration
Treating B-roll as decoration
B-roll should prove something: show the app flow, product texture, use case, result, objection, or moment the voiceover is talking about.
Approving the video before approving the script
Approving the video before approving the script
Script, claims, and pronunciation are cheaper to fix before render. If the message is wrong, do not spend credits to discover that in motion.
Forgetting the target market
Forgetting the target market
“Spanish” is not the same as “Mexican Spanish.” Localization includes examples, screenshots, people, currency, and cultural context.
Using synthetic testimonials where trust is fragile
Using synthetic testimonials where trust is fragile
For regulated, premium, legal, health, finance, or high-trust offers, avoid fake first-person proof. Use approved claims, real proof, founder-style explainers, or B-roll voiceover instead.
Retrying the same broken generation
Retrying the same broken generation
If a video gets stuck, renders unusably, or keeps drifting, stop and diagnose the cause. Tighten context, switch workflow, or report the generation instead of burning credits.
Format shortcuts
Creating videos
Choose the right video workflow and understand how video generation comes together.
Scripts
Steer the hook, storyboard, spoken line, and scene structure before rendering.
Voiceover & lip-sync
Control voice, localization, accents, and pronunciation.
Getting video right in fewer tries
Avoid wasting credits on avoidable retries.