Lovable Adds Drafts: Explore Parallel Versions of a Project Without Touching Your Live App

Lovable announced drafts on 2026-09-07. For anyone who built a site with AI and then became afraid to touch it again, this is one of the few updates this year that addresses the actual pain — but the first release has two boundaries worth reading carefully. Everything below is from the official post (verified 2026-09-09).

The old flow: edit live, and take turns

Lovable describes the previous state plainly: all of your edits happened directly in your project. Change your mind and you had to hit revert. Collaborating meant other people waited their turn or remixed the project, which made consolidating edits messy.

What a draft is

A draft is a copy of your project with its own chat and preview, where you and your team can explore different versions of the same project in parallel. You can switch between drafts and the project to compare, and — the key part — changes are applied to your live app only if you accept the draft and hit publish.

Two intended uses, in Lovable’s words:

• Bring people in. Let a teammate, a client, or your copywriter create a draft and make changes inside a real project rather than in a document full of comments. Your live app and its data stay exactly as they are, and you still decide what goes live.
• Explore several directions at once. Create more than one draft, try a different idea in each, switch between them, and keep the one that works — without gambling with your live version.

What this first release covers, and what it does not

Lovable is explicit: for this first release, drafts cover changes to your app’s front end. Anything that changes your database structure or your login setup still happens in your project’s chat.

What you can explore in a draft today:

• New colors, fonts, or a fresh layout
• Headlines, subheaders, and calls-to-action — keep the version that performs best
• New imagery, illustrations, or video
• Scroll animations, an image carousel, a sticky nav bar
• A promo or announcement bar
• Sharper copy everywhere, from button labels to empty states to your 404 page

One line is easy to skim past and matters a lot: drafts currently work against your published application’s database. Your draft is not touching a sandboxed copy of your data — think that through before testing anything that writes records. Lovable says it is working on expanding the types of changes drafts support.

How to use it (per the official post)

1. Open a project, click its name at the top of the editor, and hit New draft.
2. Start prompting to edit the draft. You can create as many drafts as you like.
3. When you are happy, hit accept and the draft’s changes are applied to your project.
4. Hit publish to make it live.
5. Changed your mind? Revert, or delete the draft and create a new one.

Not stated in the announcement (logged as unverified): whether drafts consume credits, and which plans include them. No plan tier or billing detail appears in the post. Current pricing is on our Lovable tool profile.

Our read: this is what turns AI site building into a team tool

The biggest psychological blocker with AI-generated sites is that every edit lands on the live version. Drafts separate exploring from shipping — effectively adding the branch-and-preview step that normal development already has. The real limitation is that it is front-end only: the database and auth layers still change your production environment the moment you touch them, and those are exactly the changes most likely to break something.

So the correct use today is clear: put every visual, copy, and layout experiment in a draft; keep structural and permission changes in the main project, done slowly, with your own backup.

Sources

• Lovable blog, “Introducing drafts: an easier way to collaborate and explore new ideas,” 2026-09-07: https://lovable.dev/blog/introducing-drafts
• Our pricing verification record: Lovable tool profile

Last verified: 2026-09-09