Plain-language builds
Describe an app or a site and get a complete first version: files, layout, logic, and sensible default content. Underspecified requests are filled in with conventional choices rather than left as a skeleton.
Features
Everything the builder does
A complete list, without the marketing adjectives. If something here matters to you, it works today; if a capability is missing from this page, assume it does not exist yet.
Building
Clarifying questions, at most once
If a request leaves something genuinely open, you get one short round of up to three product questions with suggested answers. They are never about technology, and skipping them is always allowed.
A progress checklist
Longer builds show a live checklist in plain language, so you can see what is being worked on and what is left instead of watching an opaque spinner.
Attachments
Drop in images, a logo, PDFs, CSVs, or text files. They are saved into the project and referenced by path, and the builder reads the ones it actually needs to see.
Multi-file projects
Anything beyond a single page is split into separate files and folders, edited surgically rather than rewritten wholesale, so later changes stay fast as the project grows.
Follow-up suggestions
Each turn ends with a few specific next steps for your app in particular, based on what it already has. Tap one to send it, or ignore them entirely.
The preview, and editing what you see
Live preview
The app runs beside the conversation and reloads with every change. It is the real app, not a rendering: you can click through it, type into it, and use it exactly as a visitor would.
Automatic error repair
After each change the preview is reloaded and watched for runtime errors. Anything it throws goes back to the AI, which reads the file that broke, fixes the cause, and re-verifies. A turn is not reported as done until the app runs clean.
Click to edit
Arm the element picker, click any element in the running app, and describe what should change about that specific piece. No more explaining which of the four cards you mean.
Direct visual edits
Adjust spacing, color, size, and type on a selected element and watch it update live. Apply commits the result to a stylesheet of your own, which the AI leaves alone on later turns.
Version history
Every turn is snapshotted with a short description of what changed. Restore any earlier version in a click, and a safety snapshot is taken before a restore so the restore itself is undoable.
Responsive checking
Resize the preview to see the app at any width, and ask for changes that apply to one width in particular.
Shipping
One-click publishing
Publish puts the app on its own public address on puter.site. No hosting account, no deploy pipeline, no build to wait on. Unpublishing is equally immediate.
Private draft links
Share a link to the work-in-progress preview without making anything public, so a client or a friend can look at it before you decide to publish.
Installable apps
A web manifest and a complete icon set are generated for every app from its own title, colors, and icon, so anyone can install it to a home screen and launch it full screen.
Download the project
Export the whole project as a zip whenever you want. It is standard HTML, CSS, and JavaScript with no build step, so it will run on any static host, or straight off your disk.
Duplicate a project
Copy a project to branch off a variation, keeping the original intact. The copy gets its own preview, its own history, and its own publishing.
Project management
Rename, search, and organize your projects in a sidebar, with a screenshot of each so you can find the one you mean at a glance.
What your app can use
Apps built here can call Puter.js, so the usual backend checklist is already done and already authenticated. See the Puter.js documentation for the full API.
Key-value storage
Per-user records, settings, and app state, with no schema to define and no database to run.
File storage
Real files: uploads, exports, generated images, documents, all stored under each user's own account.
Authentication
Sign-in with Puter accounts. No user table, no session handling, no password reset flow to write.
AI models
Chat, vision, and image generation callable from inside the app you built, without holding a provider key.
Serverless workers
Deploy backend code from the same conversation for shared state, webhooks, scheduled work, or a public API.
Peer-to-peer
Video and voice chat, screen sharing, multiplayer, and live collaboration without running signalling infrastructure.
Hosting
Static hosting on puter.site for both the draft preview and the published site.
The user-pays model
Each person using your app brings their own account for the storage and AI they consume, so your costs do not scale with other people's usage. How it works.
The builder itself
Runs in the browser
Nothing to install and nothing to keep updated. Open a tab and start, on macOS, Windows, Linux, ChromeOS, or a phone.
Works on mobile
On phones the chat and preview become two views you switch between, with the toolbar adapting to the space. Long builds keep running while the screen is on.
Survives interruptions
A build interrupted by a dropped connection or a suspended tab resumes rather than dying, and transient failures are retried automatically without you losing the turn.
Installable itself
The builder is a progressive web app: install it and it opens like a desktop application, with the shell available even before the network is.
Light and dark
A proper dark theme throughout, following your system setting by default and overridable per device.
Built on open source
The builder runs on Puter, which is open source, and the apps it makes are standard web files with no proprietary runtime. Nothing you build here depends on a format only this tool can read.
The feature list is shorter than the thing it describes
Two minutes with the builder tells you more than this page can.
Open the builder