Guide · Creator Studio

Make a brand's posts, ads and product demos

Set the brand once, its colours and fonts, and every piece comes out on it. Start from a template or a blank page, record your site for a demo, let your AI design in code, check the piece before it goes out, and export every format at once.

Open the studio →

The one idea: a post is a stack of layers

Not a picture. A document: a size, a background, and an ordered list of layers painted from the bottom up. Once that clicks, everything else in the studio is obvious.

Content layers, which add something

A solid colour. A gradient. An image. Particles. A shape. Text, with its own size, tracking, wrapping, shadow, stroke and glow.

Adjustment layers, which change everything below them

Duotone, tint, grade, posterize, grain, scanlines, vignette, blur, bloom, chromatic shift. Exactly like a real editor: an adjustment sitting on top of three layers restyles all three at once, and moving it changes what it touches.

This is why the studio does not need presets for everything. A look is a stack, and a stack can be saved, copied onto another post, or handed to your AI as text.

Three sizes cover the platforms: square at 1080 by 1080, portrait at 1080 by 1350, and story at 1080 by 1920. You can also give exact numbers.

Product demos: record your site

Give the studio a page address and the steps (click this, type that, scroll). It films them in high resolution with no real mouse, then the take lands in your piece already edited:

Dead time cut

Only the moments around each step stay. Loading and waiting are gone.

A camera that follows the action

It pushes in on each click and typed field, then eases back out between distant steps.

A drawn cursor

It moves straight to each target in about a second, taps a field before typing and shows a ring on each click. Its shape, colour and size are yours.

A device around it

Browser, laptop, phone or tablet, drawn in code at any size.

Every one of those is a layer you can still change: the cuts, the camera keys and the cursor path.

Your AI designs in code, and the studio makes it better

Many AIs now design by writing code. The studio keeps that freedom and adds what code alone lacks. A code layer takes canvas, WebGL shader, SVG or HTML and CSS written by your AI or by you, and the studio gives it:

A timeline

The code receives the time, the progress through the layer, easing curves and a seeded random, so motion is exact and repeatable.

Your brand

Colours and fonts arrive ready to use, so the code stays on brand without copying values around.

Eyes

Your AI can render frames of its own design, look at them and fix what is off, and it gets errors back with the line number.

Checks and export

Code layers pass the same checks as every other layer and export frame by frame with the rest of the piece.

Reuse

A code layer that works can be saved as a new layer type and added to any piece by name.

Code layers run in a sealed sandbox: no access to your account, your cookies or the network.

Check before it goes out, in every format

Objective checks

Text cut off or hidden under the app buttons of Reels, TikTok or Shorts, text too small for a phone, flashes and dark dips, text that is not in English, and missing formats.

Past decisions as references

What was already decided for this brand is shown next to the checks, so you can weigh it for this piece.

Every format at once

Vertical 9:16, feed 4:5, square 1:1 and YouTube 16:9 share the words, timing and music; each one is fitted to its own safe area.

Where images come from

Four sources, and they mix freely inside one post:

Your own file

Anything on your disk, including a render you made in VibeGen. Transparency is preserved, so a cut-out sits over a gradient properly.

Your library

A folder of your own material, searched by tag, so a brand can reuse its own photography without hunting for it.

Open sources

Openverse, and Pexels, Unsplash or Pixabay with your own key. License-clean stock, fetched into the layer.

A direct link

Any URL.

The two tabs

Compose

The editor. Add layers, drag them, restyle with an adjustment, export at full resolution. This tab is free for everyone, in full. A brand picker at the top sets colours, fonts and defaults, so a new post starts on-brand instead of from grey.

Feed

Not an editor: a mirror. It shows how the account will READ once everything is up, because on a profile people see rows of three, not one post at a time. Covered below, because it has a rule worth knowing.

The feed, and why it opens half-closed

The grid shows what is still to come on top and what is already on the profile underneath, in that order, because that is where they will actually sit once the queue drains. The point where the two meet is the seam, and it is the only part most people need to look at, so the grid opens showing just that: the next three out and the last three up. The arrow above it opens the rest.

The reason this view exists at all: a repeat that looks fine in a list looks terrible in rows of three. Sorting a queue alphabetically groups every variation of the same piece together and produces four identical-looking rows. Judge a feed in rows, never in a list.

Drag to reorder

Move a scheduled tile and the dates stay where they are. The pieces move between the dates; the calendar does not move with them.

Click to rewrite

Open a scheduled tile to edit the caption it will go out with. Published tiles are read-only: that text is already out in the world.

Already up

Choose how many live posts to show under the queue. Zero shows only what is coming.

The two panels above the grid

Both read from the machine that actually runs the work, never from a local copy, and both refresh themselves when a run finishes.

Posting

How many pieces are waiting, how often one goes out, whether they publish as video or image, when the next one goes, and how many days of runway are left before the queue empties.

Engagement

Likes given, follows made, comments left, and how many people the bot has found in your niche. Open the detail and you get a row of bars per kind of action, the daily caps, and whether the numbers have been checked against the platform itself or are still only the bot's own records.

That last line matters more than it looks. A bot's own log is a claim, not a fact: a button can report success without doing anything. When the panel says the numbers are unchecked, treat them as unchecked.

Driving it from chat

The studio has an MCP, so your AI can build a post layer by layer, apply your brand, fill a queue and read the panels back to you, without you touching the interface. The editor and the chat are two doors into the same document.

Free

The layer editor in full, and the MCP installs. Exports carry a small badge.

Pro, monthly or once

No badge, plus reels and video, custom fonts your AI downloads on demand, and effects it can invent at runtime.

The shortest path to a real cadence

Set your brand once

Colours, fonts, defaults.

Build one post you like

Then save the stack. That stack is now your template.

Fill a queue from it

Same stack, different content, different seeds.

Read it in rows before you schedule

Open the feed and look at it as rows of three. Fix the repeats there, not after they are up.

The engineering behind the engine, the bots and the traps they cost us lives in the journal Run a Social Media Autopilot, on the journals page.