You're about to build a FlutterFlow template, and you want it to sell. Before you open the builder, read one table in the submission docs. A full template app on the FlutterFlow marketplace carries a $400 minimum price, a UI kit or a Library carries $50, and pages, components and custom code cannot be monetized at all (FlutterFlow submission docs, retrieved 30 September 2026). Those few lines decide more about whether your item can earn anything than any amount of screenshot polish.
First action: decide your item type today, because it sets your price floor and whether you can charge at all. I have eight items on the FlutterFlow Marketplace, and the sales figures below come from my FlutterFlow Marketplace case study, which records the public labels checked October 1, 2026. Treat them as dated sales bands and rounded downloads, not exact counts.
What Sells on the FlutterFlow Template Marketplace?
Only Template Apps and Libraries can be monetized, so the first thing that decides whether a FlutterFlow marketplace template can sell is its item type, not its screenshots. Pages, components and custom code cannot carry a price.
| Item type | Monetizable | Minimum price |
|---|---|---|
| Template App (Full App) | Yes | $400 |
| Template App (UI Kit) | Yes | $50 |
| Library | Yes | $50 |
| Page or Component | No | not applicable |
| Custom Code | No | not applicable |
The consequence is stark in one direction. If you spend three weeks on a reusable component and submit it as a Component, its ceiling is zero dollars for now. Turning it into a Library is not a dropdown change, though. The docs say Libraries have limitations, most notably no support for Firebase or Pages, and Bee Law's November 2025 walkthrough on the FlutterFlow blog lists the entry conditions: a Pro+ plan because Libraries need branching and versioning, a project never deployed to the App Store or Play Store, all errors and warnings fixed, and publishing from the main branch (Publishing to the FlutterFlow Marketplace). The deployment rule is the one that catches people: ship your demo app to TestFlight and that project can no longer become a Library. Clone the project first if you want to keep both versions.
If you have not settled whether to build inside the builder at all, the FlutterFlow versus Flutter trade-off comes first. If the builder turns out to be the wrong fit, the FlutterFlow alternatives worth testing is the other fork.
What Do My Own Listings Show About Pricing?
On October 1, 2026, the public FlutterFlow profile shows Dream Home at $75 with “10+ sales” and Schedule, now listed as Advanced Calendar Template: Tasks & Google Events, at $50 with “10+ sales”. The case study records the same dated labels. They are sales bands, so I cannot give an exact combined total.
Dream Home's $75 sits below today's $400 full-app minimum in the docs. I can't say when that floor was introduced, so don't assume a new full-app submission at that price would be accepted. Consider what a $400 floor does to a buyer: at $75 a template is an impulse purchase, and at $400 it competes with commissioning the work. That reading is my inference, not a measured effect, but it points creators toward UI kits and Libraries, where the $50 floor still allows a cheap purchase. My second batch of five widget bundles, submitted in April 2026, leans that way, and the eight templates and 40-plus custom widgets I maintain are described there.
Should Your First Item Be Free?
A free item is a reasonable first move, because it gives an unknown creator something a buyer can inspect at no cost. This is a recommendation based on my own numbers, not a documented rule.
My free PDF Viewer template has been live since May 2025 and, as of October 1, 2026, displays “1.8K” downloads (about 1,800, rounded) and four positive reviews. Downloads and paid sales are different units, so I won't compare them as a conversion rate. What the free listing does is put a working widget tree in front of people, with reviews attached to my creator profile. Free items are licensed under the MIT License, which the submission criteria state grants users perpetual rights to use, modify and distribute the project, so publish only what you're happy to have reused (Submission Criteria). The Creator FAQ adds that paid items are usually governed by a Single Use License.
Can You Edit a FlutterFlow Marketplace Listing After Approval?
Not yet: the submission docs say it is currently not possible to edit an approved Marketplace Item, and that FlutterFlow is working to add editing soon (submission docs). That page was last updated on 19 May 2025, so check it again before you rely on this.
Read that with your listing in mind. Until editing exists, the name, cover image, gallery photos, description, usage instructions and price are effectively fixed once a reviewer approves. Changing any of them likely means a new submission and a new review. This changes the order of work. Instead of assembling the listing in the last hour, do this:
- Write the listing name first and check it against existing titles. The criteria ask for a unique, professional title with relevant keywords.
- Draft the description and usage instructions before you write a widget, assuming a reader who has never seen your project.
- Make the cover 1200x800 pixels, which is the size the docs specify, and keep the FlutterFlow logo out of it, since the criteria say it can imply an official endorsement.
- Use the gallery, which allows up to four additional photos, for genuine screenshots of the actual project rather than mockups of features you did not build.
- Test your Run Mode URL in a logged-out browser. The docs ask for a demo login button using anonymous sign-in, or pre-filled demo credentials, if the link includes authentication.
- Set the price knowing you can't change it, then submit.
How Long Does FlutterFlow Take to Review a Template?
FlutterFlow aims to review a submission within 7 days, but it can take up to 30 days, or 20 business days, depending on volume and complexity, so plan against the ceiling rather than the target (Creator FAQs).
A month of latency means a template with a seasonal hook needs submitting well ahead, and a rejection costs you another cycle. A rejected item returns to draft with emailed feedback naming the criteria it missed. The published criteria give you a checklist to test against: anonymous or demo access, an organized widget tree, high-resolution images at the right size, no FlutterFlow logo in the cover, no unlicensed copyrighted material, and no dependencies between libraries (submission criteria).
The bar above that checklist is less predictable. One creator wrote in the community forum that a custom video player component they had spent over eight months building was rejected with the reason that it "does not meet FlutterFlow standards" (community thread). That is one person's account, and I can't judge the verdict. The lesson I take from it is a recommendation: submit something small first and learn what the reviewers enforce before you spend months on a big item.
Can You Sell a FlutterFlow Template Somewhere Else?
No. The Creator FAQ says you cannot sell FlutterFlow projects on other marketplaces and points to the non-circumvention clause in the Marketplace Terms of Service. Distribution is single-channel, which makes the review queue a dependency rather than one option among several.
What Happens When a Bad Review Lands?
You can dispute a review only in four cases: spam or abuse, misuse of the review system, a critical misunderstanding of the item's purpose, or issues resolved after a significant update.
Good-faith criticism stays up. Reviews that represent a real user experience, or critique quality, usability, documentation or performance in good faith, are not removed just for being negative, even if subjective. You email marketplace@flutterflow.io with a link and a short explanation, and the team responds within 10 business days (review dispute guidelines). My inference: the best defence is clear usage instructions, because "misunderstanding" is the removable category you can influence in advance.
Refunds follow a similar logic. The marketplace keeps a no-refund policy because buyers get immediate access to the code, but if a defect is confirmed FlutterFlow reaches out to the creator and may refund if the defect isn't addressed within a reasonable time, handled manually in 5 to 10 days (refund policy). Consider a buyer who reports a broken widget. How fast you fix it decides whether a refund happens at all. If the template work is really a proxy for wanting a two-sided platform, that is a marketplace app build, with different economics, and the Flutter tooling I reach for is the short list.
Open the submission docs, pick your item type, and write your listing name and usage instructions before you build anything. Which one of your half-built projects would still make sense as a Library?