One project can contain several channel-specific Pages while keeping a single document authority. Each page owns ordered native Layers, and every durable change passes through the same undoable command boundary.
A Feed page, Story page, and square page can share one campaign direction without being scaled copies. Each Page owns its exact width, height, background, and ordered Layers so crop and hierarchy can be reviewed for the placement.
Layers preserve editability
Text, shapes, and images stay separate. Selecting and transforming them changes the DesignDocument through typed commands. Canvas rendering and resize handles are interaction surfaces; they do not become a second durable layer model.
Undo is immediate history
Undo and Redo walk the current command history. A drag gesture commits once at gesture end, so undo returns the layer to the meaningful previous position instead of stepping through every pointer movement.
Versions are named checkpoints
A Version is an immutable snapshot used for compare and restore. Restoring does not replace the editor with a second live state; it enters the same command history as an undoable restore operation. Image bytes remain in the Asset store.
No. Undo is transient command history. A Version is a named immutable snapshot you can inspect and explicitly restore later.
Can a generated campaign include multiple formats?
Yes. An approved Campaign Set compiles every format into editable designs with native layers in one command batch, preserving one document authority.
Cookie choices
Your cookie choices
Necessary cookies and similar storage keep sign-in, security, and private workspace recovery working. Retake uses Google Analytics Consent Mode for basic website and product measurement; you can separately allow analytics storage and Google One Tap.
Choosing necessary only keeps analytics and advertising storage denied. Google Analytics can still receive cookieless measurement signals, but Retake does not send prompts, files, project identifiers, or card details.
