Magic Patterns

Only AI generation. The credits guide says prompting, agent mode and component generation use credits, and the cost scales with the input and output tokens of each request. Manual edits, visual edits, “Fix with AI”, retries, exports and sharing use none. Magic Patterns publishes typical figures from real designs: about 70 credits for one generation, 100 for two or three versions, 110 to 200 for a small prototype of four to ten versions and about 400 for a full page or flow. Those numbers were measured with Claude Opus 5.5, so another model changes them.

Two habits move the count most. Every follow-up prompt carries the earlier conversation as context, which raises the cost of later replies; the /Clear command resets it when you start an unrelated change on the same design. And a cheaper model is not always cheaper: the guide warns that retries with a weaker model can cost more than one pass with a capable one. Plan mode, where the agent drafts a plan before writing code, also spends credits.

More than credits. The Terms of Service say that on the Free plan Magic Patterns may use your inputs and the designs you generate to train and improve the service, may show those designs in public galleries and promotional material, and may add a “Built with Magic Patterns” attribution to public-facing work. On paid plans the Terms say your content is not used for training and is treated as confidential information.

The Free allowance itself is described only as “free monthly credits”, and the pricing FAQ calls the free tier limited. The plan table in the docs leaves design systems, GitHub sync, the MCP server and on-demand usage off Free, so a team that needs its own components in every design starts on Starter.

Yes; the docs say every design is a website. You add pages by naming a route in the prompt, such as /settings, and that path becomes part of the live address when you publish. Publishing from the Share menu gives the design a random Magic Patterns address. A chosen address such as project-my-portfolio.magicpatterns.app is a paid feature. To use your own domain, the custom domain guide asks for an A record to 149.248.202.188 on a root domain or a CNAME to magicpatterns.dev on a subdomain; the metadata guide says this route needs no paid plan, but hiding the badge does.

Published designs can sit behind a password, and since 4 August 2026 new designs are private until you publish or invite people. What the docs do not give is any traffic, bandwidth or form limit for published designs. If you are choosing a host for a marketing site, the Framer profile lists its page and bandwidth limits per plan.

Six routes start from the same design, according to the export overview. A zip download hands over the code. GitHub sync, on paid plans, creates a new repository from a React and Vite template and syncs both ways, and Magic Patterns keeps every version when you pull changes back. “Copy code as prompt” packs the code for pasting into an AI editor, and an integration skill teaches Cursor or Claude Code to adapt it to your conventions. Figma export copies a static snapshot of whatever is on screen, so open menus or states must be set before you export, and interactivity does not carry over.

The v3 API creates designs, sends prompts, reads and writes files and publishes, drawing on the same credit balance as the web app; calls that need credits return 402 once it is empty. If you would rather have a coding agent drive a design canvas without spending that canvas’s own credits, the MagicPath profile explains how it bills agent work.

Plans are per paid seat inside a team workspace. You can invite unlimited members on free seats, which get the free monthly credits; a paid seat gets its own monthly credits and full access. All paid members must be on the same tier. Starter allows up to 10 paid seats, a workspace with 11 or more needs Business or Enterprise, and Enterprise starts at 10 paid seats. When someone leaves, an admin can reassign the paid seat, and credits already used on it move with the seat.

Downgrading or cancelling never deletes projects or code; you keep viewing, editing and exporting them without the plan’s features. For refunds the docs point to support@magicpatterns.com, while the Terms say ending the agreement does not entitle you to a refund of prepaid fees unless agreed in writing. Rolled-over credits are non-refundable.

1. Create a design and ask for a home page with routes /services and /contact, each linked from the navigation.
2. After every reply, write down the credits and model shown under the response, and use visual edit for text changes.
3. Publish from the Share menu, open the random address on a phone and check that both routes load.
4. Download the zip, follow the instructions it contains to run it locally, and compare it with the preview.
5. Try Export to Figma on the contact page and note what arrives as layers.

Accept if the three routes work in the published site and the local build, and the credit total stays inside your free allowance. Reject if the free credits run out before the third page, the zip does not build, or the training clause rules out putting client material into a Free design. No result is recorded here.