How revisions work
Marcus treats every instruction as a conversation. If it generates a hero section that feels too bright, a product page with overly formal copy, or a layout that doesn't match your vision, you say so. Type something like "make the hero darker" or "use friendlier language" into the chat, and Marcus revises the page in a few seconds.
You're not editing code or hunting through menus. You describe the change the same way you'd ask a colleague to adjust a design. Marcus applies it, updates the live preview, and saves the new version to your project history.
What you can ask for
Marcus handles visual changes, content tweaks, and layout adjustments through natural language. You can request a different colour scheme, swap out images, shorten headlines, rearrange sections, or change the tone of the copy. Each instruction is interpreted in the context of the page you're working on.
If you want a photo replaced, say "use a different photo for the team section" or "swap this image for something warmer". If the text feels too long, try "cut this paragraph in half" or "make the pricing copy shorter". Marcus revises the specific element you mention without reworking the entire page unless you ask it to.
Revision speed and limits
Each revision completes in seconds, not minutes. The underlying model—Anthropic Claude—processes your instruction, updates the relevant HTML and CSS, and renders the change in the editor. You see the result immediately in the live preview.
There's no hard limit on revisions. If you're on the Builder plan (€29 per project per month), you can iterate as many times as you need within a single project. The free tier covers one project with up to five pages, and revisions work the same way. Studio subscribers managing up to 25 projects get the same revision flow across all sites.
Rolling back to earlier versions
The app shows the current version only and has no rollback button. If a change might take the design in the wrong direction, download the ZIP first; if it does, describe the earlier look in your next revision or start a fresh project from your original brief.
This isn't an undo button that steps backward one change at a time. It's a timeline of every saved state. You choose the version that worked, restore it, and continue. No changes are permanently lost unless you delete the project entirely.
When revisions don't fix it
Sometimes the issue isn't a single element—it's the overall direction. If repeated revisions aren't getting you closer, the fastest fix is to roll back to an earlier version that felt right, then give Marcus clearer instructions from that point. Be more specific about what you want: "use a two-column layout instead of three" instead of "change the layout".
If you're stuck, try describing the outcome rather than the method. Instead of "make this button bigger", say "the call-to-action needs to stand out more". Marcus interprets intent and applies changes that match the goal, not just the literal instruction.
Exporting after revisions
Once you're happy with the result, you export the project as a ZIP file. That package contains the final HTML, CSS, images, and assets from your last saved version. The exported code is clean, self-contained, and ready to host anywhere. You're not locked into Marcus after export—the files are yours.
If you make further changes after exporting, you export again. Each export reflects the current state of the project. There's no versioning applied to the ZIP itself; it's always a snapshot of what's live in your editor at the time you download it.
Revisions and collaboration
If you're working with a team, project history shows who made each change and when. This matters when multiple people are iterating on the same site. You can see which revision introduced a specific design decision and roll back to a version before that point if needed.
Each project has one owner, who runs the revisions. The process is the same on every plan: describe what you want, see it update, and keep the ZIP of any version you like.