CodeCanyon Regular vs Extended License for Flutter Apps

You bought a $29 Flutter template on CodeCanyon, took the Regular License because it was the default and the cheaper option, and shipped your app free. It picked up enough users that you are now building a monthly Pro tier. Somewhere between creating the subscription product in the store console and designing the paywall screen, you go back to the license page and read the line about end users paying. Your stomach drops a little.

That moment is the CodeCanyon regular vs extended license question in its most expensive form. You are no longer asking which one to buy. You are asking whether you already bought the wrong one. The answer turns on a single test that most write-ups phrase badly, and it has less to do with making money than you would expect.

The license is one of several things worth checking when buying Flutter app templates, alongside code quality, maintenance, and whether the app needs a server at all. It is the one that costs real money when you get it backwards, because the mistake usually surfaces after launch.

Some context on where this comes from: we sell our Flutter apps direct through Gumroad and also list them on CodeCanyon and Codester, so we deal with these rules from the author side as well as the buyer side. Our direct sales use the same two options and the same end-user test described below. Everything below about Envato's terms comes from CodeCanyon's own license pages as they read on 10 November 2026, not from memory or another vendor's summary. Where those pages do not answer a question, we say so.

What the license actually gates: whether end users pay

The usual framing is personal use versus commercial use. It is wrong, and it causes most of the confusion.

The Regular License terms set out a different test. They count an end product as free when it is not sold, when the end user pays no fee to access it, and when nobody pays a subscription fee for a service that includes it. CodeCanyon's license overview puts it more briefly: if the end product will be free to the end user, you need the Regular License, and if the end user must pay to use it, you need the Extended License.

Notice what is missing from that test. Nobody asks whether a business is involved, whether you make money from the project, or whether the product promotes something you sell. A company's free customer app is commercial by any normal definition, and it can sit on a Regular License. The question is narrower: does the person using the finished product pay to get at it?

The second rule matters just as much. Both licenses cover one end product. Neither is a bulk license: the Extended License changes what your one product can charge for, not how many products you can build from the purchase. Ship the same template as two branded apps and that's two licenses. Check the license overview's on-demand row if you run a white-label business.

The SaaS trap: when a free app grows a paid tier

CodeCanyon's License FAQ is direct about the case that catches founders. If end users need to pay to see the end product, you need the Extended License. The Regular License terms close the subscription route as well: a fee paid to subscribe to a service that includes the end product takes it outside their definition of free.

For mixed models the FAQ adds a nuance: what matters is where the item is used. If the item only appears in the free part, Regular is fine. If it is used in a part people must pay to access or use, you need Extended, and the FAQ applies that whether users pay up front or through a revenue share.

For a website template, that nuance can save you money. If a purchased landing page template only powers your free marketing pages and your paid product is separate code, the paid part does not use the item. For a Flutter app template it almost never helps, because the template is the app. The paywall screen, the Pro-only features and the settings behind the subscription all live in the codebase you bought. Once you add a paid tier to an app built from a template, the item is in the paid part.

Here is how the timeline usually runs:

1. You launch free on a Regular License. You are compliant.
2. You add a subscription or a paid tier. From the day it goes live, part of your end product sits behind a payment and is built on the item. The Regular License no longer covers it.
3. Nothing flags this for you. Google Play and the App Store have no view of your Envato license, so no store review will catch it, and nothing in your build changes.

That third step is the trap. The license question gets answered once, at checkout, usually by someone who has not decided on a pricing model yet.

Ad-funded apps and one-off in-app purchases sit at the edge of the published wording; the scenarios below cover both.

Already past step 2? For going beyond what your license covers, the License FAQ says to contact the Envato Help Team with the username or email on your account and the names of the items involved. Expect to need the Extended License for that item. Do it as soon as you realise, not after a bigger audit finds it for you.

Freelancers and client work: your fee is not the test

If you are a freelance developer building apps for clients, this part is for you, and it is mostly good news.

Under both the Regular and the Extended License you may charge your client for creating the end product, and the Regular License terms let you transfer that single end product to the client for any fee. Your invoice to the client does not change the license. The client's end users do.

The same logic runs the other way. If your client's app will charge its users, the client needs the Extended License, however little you charged for the build.

Handing the work over is allowed. The License FAQ describes a freelancer's purchase as "essentially buying the file on your client's behalf". You can transfer the end product to the client, point them to the license terms, and then delete the item from your own machine.

What we could not find on the license pages is a way to move a purchase from one Envato account to another. The FAQ says licenses are generally not transferable, and its exceptions cover the license following the end product to a client or buyer. Plan as if the purchase record stays with whoever bought it.

That shapes how you set up an engagement:

• One license per client job. CodeCanyon's license overview is clear that one license cannot be reused across several clients or jobs. Five clients on the same template means five purchases.
• Settle the payment model in the scope document. Ask whether the app will ever charge users before you buy anything, and write the answer down. It decides which license you need.
• Decide whose account buys it. If the client wants the purchase on their own record, have them buy it under their own account from the start. We found nothing that lets you move it later.
• Document the handoff. Record the item, the license type and the purchase in your handover notes, then delete your copy as the FAQ asks.

CodeCanyon regular vs extended license at a glance

	Regular License	Extended License
End users pay to access the end product (purchase, subscription, paywall, paid members area)	Not covered	Covered
Free end product, even if commercial or built for a paying client	Covered	Covered, but not needed
Paid tier of a freemium app built with the item	Not covered	Covered
Free app funded only by ads	Not named by Envato; reads as free	Covered
End products per purchase	One	One
Reuse across several clients	No, one license per client	No, one license per client
Price	The item's base price	Set per item; the examples below run from roughly 3x to 11x
Who usually needs it	A freelancer building a free app for a client, or a founder launching free with no paid plans	A founder charging subscriptions or putting features behind a paywall

Sorting this out after launch costs you a support ticket with Envato, an Extended License at whatever that item sells it for, and a stretch of time in which your paid tier ran on a license that did not cover it. The cheaper route is to choose your payment model first and buy from an author who will tell you plainly which license it needs. That is the standard we hold our Flutter and Bootstrap templates to. Ten of our eleven Flutter apps store everything in an on-device Hive or Isar database with no server behind them, so the license is the main cost you have to plan up front, and if your model is unclear you can ask us before you buy.

Worked scenarios: which license each app needs

Here are five common set-ups, the license each one points to, and where the published wording runs out.

One free app for one client

A clinic pays you to build a booking app its patients download for free. That is one Regular License for this client. Patients pay the clinic for treatment, but that is a separate service, and the FAQ says payment for something separate from the item does not require Extended. If the clinic later wants a paid members' area in the app, it needs the Extended License.

A paid download or in-app purchases on the stores

Publishing to a store is fine in itself: the FAQ lists putting a compiled game starter kit on an app store as a permitted end product. The price tag decides the license. A paid download is a sold end product, which the license overview rules out under Regular. In-app purchases that switch on paid features land in the same place, because those paid screens are the template's code. Budget for Extended either way.

A free app with ads

Envato's pages do not name this case. Nobody pays to access an ad-funded app, so against the Regular terms' definition of free it looks like a Regular License case. The FAQ's answer about advertising covers using an item inside an advertisement, such as a commercial, not an app that shows ads. If the app's revenue matters to you, get Envato's answer in writing. Apps bought direct from us follow the same rule as CodeCanyon, so the same reading applies to them.

The ad plumbing is its own job. An ads SDK, a consent form that runs before any ad loads, a frequency cap and test ad IDs for debug builds are all work you do before the first ad earns anything. Our SubZero offline subscription tracker ships with AdMob interstitials and Google UMP consent already wired in, capped at two per session, with Google's test ad IDs in debug builds and no server to run.

SaaS or a subscription

The clearest Extended case: the Regular terms name a subscription fee for a service that includes the end product as something that stops it being free. One SaaS catch goes further. If your service lets each customer generate their own customised product from the item, such as a builder that turns out a branded app per customer, the Extended License does not cover it. The Extended terms call it a single application license and ask for one license per product a customer creates.

The same app for several clients

Three salons want the same booking app with their own name and colours: three end products, three licenses. Extended does not change the count. Each license then follows that client's own model, Regular for a salon whose customers book free, Extended for one selling a paid tier in the app. If you resell a white-label version, price one license per client into the first quote.

Buying direct on Gumroad vs on CodeCanyon

For the license test, where you buy our apps makes no difference. A direct purchase on Gumroad has the same two options in a dropdown at checkout, Regular at $29 and Extended at $99 for each of our Flutter apps, and the same line between them: whether end users pay, with one end product per license.

What differs is the paperwork. On CodeCanyon, Envato's license text governs the purchase, and your proof is the purchase code and license certificate on your Envato Downloads page. On Gumroad you buy from us, under our terms of service, which describe a direct license as non-transferable and tied to the use chosen at purchase; your proof is the Gumroad receipt, and the files stay in your Gumroad Library. For a client job bought direct, the simplest route is for the client to buy on their own email so the receipt is theirs from the start.

Neither route has an activation step. Our apps do not check a key when they run, so the receipt or purchase code is the only record of which license you hold. Our help article on where to find your proof of purchase shows each place step by step. Some of our apps are also on Codester, which has its own terms; we compare CodeCanyon vs Codester for buyers and sellers separately.

How big is the price gap?

You will find confident multipliers quoted online. We could not verify any of them as a rule, and Envato's license pages do not publish one. Each item page lists its own price per license, and that is the only number that applies to your purchase.

These are the figures we could check on 10 November 2026:

Example	Where it is shown	Regular	Extended	Gap
Agri Ops (ours)	Direct, via Gumroad	$29	$99	about 3.4x
InAllCart, list price	The vendor's own site	$69	$399	about 5.8x
InAllCart, discount price	The vendor's own site	$20	$219	about 11x

Be clear about what this table is. The InAllCart figures are as shown on the vendor's own site. Its buy buttons lead to CodeCanyon checkout, but we could not confirm the CodeCanyon item page shows the same figures, and the site's Extended tier adds installation and support extras, so it is that vendor's own package. What the rows do show is that the gap is set by whoever sells the item, varies a lot between sellers, and moves with promotions: the same product shows about 5.8x at list price and about 11x at its discount price.

The practical rule follows from that. Check the Extended License price on the item page before you commit to a template. If there is a realistic chance your app will ever charge users, put that number in your launch budget now rather than finding it after the paid tier ships.

Frequently asked questions

Can I sell an app made from a CodeCanyon template?

Yes, with the Extended License. Publishing to a store is a permitted end product; if users pay to download the app or to use parts built with the item, you need Extended.

Do I need the Extended License for client work?

Only if the client's end users will pay. You can charge your client for the build under either license.

Can I upgrade from Regular to Extended later?

The License FAQ says to contact the Envato Help Team with your account username or email and the item names. For our apps on Gumroad, the Extended option sits in the same checkout dropdown as Regular, so choose it when you buy.

Will Google Play or Apple check my license?

No. The stores cannot see your purchase, and our apps have no runtime license check, which is why the mistake usually surfaces late.

Is Regular enough for a free app that sells physical products?

Usually. The FAQ says payment for a product or service separate from the item does not require Extended. If customers pay to use features built with the item, it does.

Before you buy: a short checklist

• Read the specific item's license terms and prices on its own page, not a summary (this one included).
• Decide the payment model first: free, ads, freemium, subscription or one-time purchase. If any route ends with users paying, budget for the Extended License.
• Count end products. Two apps, two brands or two clients means two licenses.
• Buy under the account that will own the product. We found no way to move a purchase between Envato accounts.
• For client work, record the item and license type in the handoff, and delete your copy after transfer.
• If your model does not fit the published examples, ask Envato support in writing before the paid tier goes live.

If you are still deciding whether a template is the right route at all, we compare buying an app template with building from scratch separately. Once the license is settled and the template is bought, the harder part is usually the rebrand and the store listing. We handle that reskin and setup work if you'd rather hand it off than do it yourself.