VidVertex Docs

Docs

Every feature, explained in plain English — readable by you, and by your AI.

The pipeline: inbox, stack, render, scheduleinboxnew clipsstacklayout + textsrenderone file perbrand × platformschedulecalendar, Zernioor Metricool
FIG 1The route the chapters follow: the inbox holds new clips, a stack turns one clip into a post, the render writes one file per brand and platform, the schedule publishes them.
START HERE
01Getting startedFrom download to your first scheduled post.
InstallActivate your licenseGet oriented: the hubCreate your first brandBuild your first stackRenderPost itWhere to go from here
THE APP
02Brands & platformsA brand is a channel identity: the look, the assets, the language and the accounts of one page you publish as.
The brand editorIdentity: look and voicePosting time, language and voiceAsset pools — the shared libraryPlatforms & accountsThe brand & channel map+ 1 more
03The stack editorA stack is one piece of content and everything attached to it: the clip, its layout, overlays, captions, texts and target brands.
The canvasContent tab — the briefing deskWidgetsThe hook widgetThe endcard widgetVideo tab — format, zones and safe zones+ 3 more
04CaptionsWord-timed, burned-in captions ("karaoke captions") — transcribed locally for free, styled per brand, translated per language.
How it worksPositioning and sizeStylesThe editable transcriptTranslations (multilingual captions)Good to know
05Rendering & templatesOne click turns a stack into its variants: one file per brand × platform, each branded, captioned and technically distinct.
What a render producesOutput templates and GPU encodingThe randomizerThe render queueRender previewDisk space
06Upload & schedulingRendered files become scheduled posts: assigned to brand × platform slots, checked, and pushed out on time.
The upload modesBuilding an upload planPre-flight checksCover frameThe calendar and upload historyThe CSV's safe twin+ 2 more
07Settings & maintenanceWhere the app keeps its data, how it updates itself, and the housekeeping pages.
User profileAppearance and preferencesUpload, AI, CSV settings and labelsIntegrationsVideo, render and randomization settingsStorage and backups+ 1 more
AUTOMATION & AI
08AutomationWhen the workflow is dialed in, stop doing it by hand.
The assembly lineSchedules: the assembly line on a timerThe inboxAuto-fit and layout zonesThe review queueThe watch folder (headless job specs)+ 3 more
09AI setupBring your own key.
What needs a key, what doesn'tProvidersVoiceover (TTS)Labelling AI contentPromptsCosts and data
10Connect VidVertex to ClaudeLet an AI assistant run the app for you: "set up these ten brands", "build a stack from the newest clip, write the hooks, render a preview and show me", "what's…
What you getClaude Desktop and CoworkClaude Code, Codex and other MCP clientsWhat to ask for
11Agent control (MCP)VidVertex ships an MCP server — the open standard AI assistants use to operate software.
ConnectingWhat the assistant may do — and what it may notA tool reports what it didThe toolsWhat this looks like in practice
12MCP tool referenceEvery tool the VidVertex MCP server exposes — 105 in total — with its parameters, generated from the server's own tool list (03.09.2026).
Reading stateCreating and producing postsEditing stacksBrands and the asset libraryOrganizing, automation and housekeeping
MORE
13DownloaderThe free companion app: paste links, get files — straight into your VidVertex inbox if you want.
Install and first downloadWhere files goLogin-gated links and rightsThe handover workflow (with VidVertex)
14Google Drive setupMetricool takes media as public links, not as file uploads.
Why this is a one-time choreCreate the OAuth clientConnect VidVertexWhat an upload run does nowIf something goes wrong
15FAQ & troubleshootingThe problems that actually come up, and what to do about them.
Install & startupLicense & updatesCaptionsRenderingPostingAssistants (MCP)+ 2 more