[Documentation](https://fluxnative.app/docs) / Designs and templates

# Templates

Copy a full app or a screen design into your organization, then follow its setup checklist: make it yours, try it, connect your backend.

![The template catalog with Use template on each card, then the Create from template dialog with the workspace, the new app's name and Use template](https://fluxnative.app/guide-media/templates.ade019de.webp)

Pick a released template, name your copy, and follow its setup checklist.

## Steps

1. Open **Templates** and pick one. A full app has its services; a design is screens on sample data with no backend. Each card shows its screens, its price and the backend it needs, such as **Needs Supabase**.
2. Click **Use template**, choose the organization and name the app.
3. Follow the setup checklist pinned above the copy's chat. It starts with **Make it yours** (name, language, currency, colour); a template that needs a backend offers **Try it with sample data**; a step whose backend is not connected shows **Open Server**.
4. Send each step's prompt to the assistant, then tick the step.

## Good to know

- Forking spends no credits, but the plan's project limit applies and you need permission to create apps.
- A paid template is **Premium**: a complete, production-ready app such as [FluxNative Commerce](https://fluxnative.app/docs/fluxnative-commerce), bought by the **site**. A site is one website, with unlimited apps and native builds for it. Every site costs the template's price, and some templates take a percent off a purchase of several sites. It is one payment, not a subscription: later releases are included, and an app you made changes only when you update it. Buying needs permission to manage billing. Bought ones are under **Purchased**.
- Every purchase is listed under **Credits & billing** › **Your products**, with its sites and **Buy another site**. Before an app's first native build, open **Build** › **Connect website** and confirm: the website is the URL in the app's `.env` (for a store app, the store's address), and connecting needs permission to edit code and manage billing. Other apps of the same website use the same site; another website needs another site. Only support moves a site to another website (**Request website change**): changing the URL in the source does not move it, and its builds are refused. The preview and editing work without a connected website; native builds and taking the source out need it. After a refund, the purchase's sites no longer build.
- A Premium template's apps don't count toward the plan's app limit, and once their website is connected they build and go to the stores on every plan, Free included.
- A copy never includes the author's backend or data, and it is not deleted if the template is unpublished or refunded. You own the app made for you; the template's code stays InspireUI's and is licensed for use in your apps ([Terms › Our intellectual property](https://fluxnative.app/terms#ip)). Ask support before reselling it or publishing it as your own work. FluxNative Commerce has its own licence: [Terms › FluxNative Commerce](https://fluxnative.app/terms#commerce).
- The template's page says whether it was made with the current version of FluxNative. A copy of an earlier one works, without newer features such as app languages and currencies, until you ask the agent to update it.
- Only templates with a verified release can be used; others show **Coming soon**. No match? Choose **Build it from a prompt**.

## Related

[Server](https://fluxnative.app/docs/connections) · [Start a project](https://fluxnative.app/docs/start-a-project) · [FluxNative Commerce](https://fluxnative.app/docs/fluxnative-commerce)

Previous: [Build from a Figma design](https://fluxnative.app/docs/figma) · Next: [Explore and Validate an idea](https://fluxnative.app/docs/explore)

---

Copy a full app or a screen design into your organization, then follow its setup checklist: make it yours, try it, connect your backend.

Page: https://fluxnative.app/docs/templates