Autodesk Flex tokens in 2026. What a day costs and when a named seat wins.

Flex charges a fixed number of tokens for every day a user opens a product. It suits occasional users, and it costs more than a named subscription for anyone working in a product more than about two days a week.

How do Autodesk Flex tokens work?

You prepay a pool of tokens, and each day a user opens a product burns that product's fixed daily rate: 7 tokens for AutoCAD, 10 for Revit. A ten minute session costs the same as a ten hour one. Because Flex replaces the named seat, you can give access broadly and pay only for days of actual use.

The daily rates sit on Autodesk's published Flex rate sheet. Three properties of the model decide what it costs you.

• The day is the unit. Workflows built on short, frequent looks at a drawing are the worst case for Flex, because each look is billed as a full day.
• The pool is shared. Tokens sit at the account level, available to the whole user base. That suits teams whose members take turns with a product now and then, and it is impossible to control without per user visibility.
• The pool expires. Unused tokens are lost. There is no rollover at standard terms, so every token bought above real consumption is paid for and never used.

What counts as one day of use?

A day is a 24 hour window that starts when the user opens and signs into the product. Reopening it, or running a different version of the same product, inside that window costs nothing extra.

If the product stays open past 24 hours, Autodesk charges the daily rate again. A Revit session opened on Friday morning and left running until early Monday burns three days of tokens, about $90 at list, two of them for no work at all. Closing the product stops the charges.

What does a day cost for each product?

At the $3 list rate the daily price is simply the token count times three. The breakeven column compares that daily price with a named user subscription for the same product, which we cover in detail below.

What does an Autodesk Flex token cost in 2026?

A Flex token lists at $3.00 in the US when you buy fewer than 5,000 at a time. Larger purchases step down through volume tiers to $2.40 per token at 250,000 tokens or more, 20 percent below the base rate.

Tokens expire 365 days from the date of purchase, and Autodesk gives no credit or refund for expired tokens.

Because each purchase carries its own 365 day clock, a pool bought in one order at the start of the year expires in one block. Smaller orders spread through the year expire in smaller pieces, but each small order may land in a higher price tier.

At what usage does a named Autodesk subscription beat Flex?

A named subscription wins once a user opens the product on more than about 100 days a year. At current US list prices a named AutoCAD subscription costs $2,095 a year against $21 per Flex day, and Revit costs $3,005 a year against $30 per day. Both divide out to roughly 100 days.

A full time designer at around 230 days costs more than twice as much on tokens as on a named seat. The same person at 30 days costs less than a third of the named price.

How does the volume tier shift the breakeven?

A lower token price pushes the crossover later. At the $2.40 top tier, an AutoCAD day costs $16.80 and a Revit day $24, so both products break even at about 125 days. Over a working year of roughly 48 weeks, 100 days is just over 2 days a week and 125 days is about 2.6.

That range matches what we see in practice. In our benchmarks, Revit and Civil 3D users passed the breakeven once they logged in more than 2 to 3 days per week. Your own crossover depends on the token tier you actually pay and any discount on your named subscriptions, so run it with your numbers.

Why does the team average give the wrong answer?

Say a 60 person design team runs Revit. Twenty people use it 160 days a year and 40 use it 25 days a year. The team averages 70 days, well under the breakeven, so an average based model puts everyone on Flex. The split below shows what that decision costs.

The split saves $24,800 against all Flex, about 22 percent, and every user keeps access. Note that the smaller token order lands in a worse tier and still wins, because the heavy users were the expensive part of the pool.

How should you size an Autodesk Flex token pool?

Size it from measured burn in your token usage report, after moving heavy users to named subscriptions, plus named growth. Pools sized on the number of people who might use a product always come out too large. Across our benchmarks they ran 20 to 40 percent above prior year actual consumption, even where the team had the burn log.

Sizing fails in one direction because no manager wants a designer locked out mid project, and the expiry then disposes of the evidence. A pool bought 30 percent above real burn forfeits about 23 percent of what you paid, and across the 20 to 40 range the loss runs from about 17 to 29 percent of the purchase.

Where do you find your Flex consumption data?

Autodesk Account holds it. Sign in as an admin and open Reporting, then Token Usage, and pick the team.

• Summary tab. Current balance, tokens used, a usage trend by product and a forecast of when the balance runs out.
• By Product tab. Tokens burned per product, the number of users on each and the average monthly consumption.
• By User tab. Each user's tokens, the products they opened and the number of days they used Flex. This is the column the breakeven needs.
• Export. Choose the Past 12 months range and download Excel or CSV. Custom ranges stop at 90 days, and Autodesk deletes past exports after 14 days, so save a copy each quarter.

If you buy tokens under an enterprise Token Flex agreement rather than online, admins can also pull consumption into their own reporting tools through Autodesk's Token Flex Usage Data API.

How do you turn the report into a pool size?

1. Export 12 months of usage by user and product.
2. Remove leavers, shared logins and one time project spikes that will not repeat.
3. Run the breakeven per user and product: days used times daily burn times token price, against the named subscription. Move everyone above the line to a named seat.
4. Add up the tokens the remaining users burned. That is your measured base.
5. Add growth only for named hires or projects, with a token count against each.
6. Let the volume tier follow that total. Do not round the order up to reach the next tier.

Why we disagree with buying a bigger pack for the better rate

The usual advice is to buy tokens in bulk up front, because the per token price falls and no designer gets locked out. We disagree, because the tier saving is small and the expiry loss is total. Say your Revit users measurably burn 7,000 tokens a year. Buying 7,000 at $2.93 costs $20,510.

Rounding up to 10,000 tokens earns the $2.85 tier, a saving of 8 cents per token. The order costs $28,500, and 3,000 tokens worth $8,550 expire unused. Your effective price per token actually used is about $4.07. Buy the measured amount, and negotiate top ups at the original tier instead.

What does Autodesk see in your Flex usage data?

Autodesk sees everything you see: every burn is logged per user, product and day. That record is your sizing dataset, and it is also Autodesk's compliance dataset. Installs running outside the token and subscription base stand out sharply against telemetry that precise.

The conversation about non compliant installs has become the standard opening of Autodesk's commercial escalation, which our Autodesk audit defense guide covers step by step. The safer course is to run the reconciliation yourself before Autodesk raises it.

What should you reconcile every quarter?

• Burn log. Who used which product, on how many days, from the Token Usage export.
• Entitlements. Named subscriptions and token balances assigned in Autodesk Account.
• Installed software. What your software deployment and inventory tools find on the machines.

Any install that maps to neither a named seat nor Flex access is the gap Autodesk will find first. Close it or document it. Keep the audit readiness checklist as the standing control. A team that runs this review every quarter can answer a compliance letter from a reconciliation it already holds.

What have we seen in recent Autodesk Flex renewals?

Flex was usually sold to the wrong group of users and bought in amounts well above real burn. That is the consistent finding across roughly 20 to 30 Autodesk customers I benchmarked between 2024 and 2026. Three patterns came up again and again.

1. Heavy users stayed on tokens. Revit and Civil 3D users who had long passed the named user breakeven were left on Flex anyway.
2. Pools were oversized at renewal. Bought above prior year consumption without usage data, then forfeited when the tokens expired.
3. Expired tokens were written off. Most customers lost part of the pool every year and treated it as a rounding error, because no one owned the consumption report.

Every token bought above measured burn is money you hand back to Autodesk on the expiry date.

The customers that split users by measured behavior, tokens for the occasional group and named subscriptions for the heavy one, cut their Autodesk spend by 15 to 25 percent without removing access from anyone. The wider portfolio picture, including EBAs and collections, sits with our Autodesk licensing advisory practice.

What will the Autodesk account team say, and how should you answer?

Expect the pitch to lean toward a larger, earlier purchase. These are the lines we hear most often on Flex, with the reply that holds up.

Which terms should you negotiate on a Flex purchase?

Negotiate the calendar and the price of later top ups, because those decide how much of the pool you actually use. On a large order, ask for these in writing:

• Expiry terms. An extension or partial rollover of unused tokens, since standard terms give no credit at all.
• Top up pricing. Mid term purchases priced at the original tier rate, so buying measured burn does not cost you a worse rate later.
• Tier on actual volume. Where possible, the tier applied to actual rather than committed consumption.
• Rate sheet hold. The per product daily rates in force at purchase apply to the tokens you bought, for their full life.

What to do next

1. Pull the token consumption report. Export 12 months per user, product and month from Reporting, then Token Usage. It is the only reliable input to every decision below.
2. Run the breakeven per user and product. Use the days count from the By User tab and the token tier you actually pay. Move everyone above the line to a named seat before you size anything.
3. Size the renewal pool on measured burn. Add named growth, never population, and let the volume tier follow real consumption.
4. Negotiate the calendar. Ask for better expiry terms, top ups at the original rate and a tier based on actual volume.
5. Reconcile installs against entitlements quarterly. That way the telemetry conversation is yours to open. The Vendor Shield subscription keeps the reconciliation running between renewals.

Frequently asked questions