What is the Context tab in InVideo Agent One and how do you use it?
Last updated August 1, 2026
The Context tab in the invideo agent is the project's persistent memory: one place that holds your brand identity, visual guidelines, product references, and production rules, and applies them automatically to every image, video, and ad generated in that project. You load it once — about 15–20 minutes — and stop re-prompting brand context per generation.
Think of the Context tab as the project brain the invideo agent reads before every generation. Anything stored there — visual language, tone of voice, product details, standing rules — governs each output without being repeated in prompts, which is what makes the second, third, and tenth ad in a project faster than the first.
What lives in it. Load the foundations first: your website, color palette, and tone of voice. Then add the reference material the invideo agent will pull from on every shot — visual guidelines, a product catalogue with multiple angles per product, and a treatment-style rules document that includes explicit don'ts (one production listed "no plastic-looking fabric" and "no generic AI faces" to block common failure modes). Context also absorbs what the invideo agent learns on its own: upload a reference ad and it saves the extracted camera language and pacing rules into context; ask it to research your brand and it stores findings in the project's knowledge bank — in one documented case, the agent pulled and stored market data like a brand's 150+ country footprint to inform creative direction. Specialized descriptions belong here too: one fashion production stored a written description of how each fabric physically feels, so every subsequent shot rendered fabric behavior correctly without per-shot prompting.
How to set it up. If you already have brand documents, upload them directly — one production seeded the entire project with 3 PDFs (visual guidelines, product catalogue, and a treatment note) and reused them across every ad in the project. If you don't have documents, tell the invideo agent to research your brand from its website and existing content, or jam with it conversationally to build the documents before production starts. Either way, initial setup runs about 15–20 minutes, and it's a one-time cost per project.
How it pays off in use. Once context is loaded, you direct shots, not brand rules — in one fashion production, the creator never re-prompted fabric behavior across dozens of shots because the lookbook and shot direction were already in the agent's memory. The gains compound within a project: a second ad built in the same project took 2 hours versus 3 for the first (33% faster) because zero context setup was needed, and a documented UGC pipeline settled at roughly 2 hours per ad after the initial context was established. Context is also shared across sub-agents: spin up a scripting sub-agent or a second production sub-agent in the same project and it inherits all brand and creative context automatically, with no re-uploading of references. That shared memory is also a credit-efficiency lever — once context was locked, one creator reported that fabric and environment interactions came back correct from initial generations, with iteration needed mainly on framing, which keeps regeneration waste and spend down.
One practical rule: if your brand already has guidelines, upload your own PDFs rather than asking the invideo agent to research you — your documents are the more accurate source, and the agent treats them as canonical for the whole project.
Watch some of these to see what works for you:
The context tab is basically the brain of the project. It holds all of this through every ad you build, without you repeating any of it.
— invideo's creative team