Descript Pricing: Every Editor Seat Adds to One Pool

Descript puts more of its commercial model in public than almost any vendor in its category. The plan ladder sits under a heading reading "A plan for whatever you create" in both billing states, the two usage meters have their own help centre article, and the top up rate card is printed as a table with a per unit price beside every bundle.

The number that decides what a go to market team pays is still not on the pricing page, because it is not a price. It is a denominator. Two of the three allowances Descript meters are counted per Editor seat and pooled into one shared drive, the third is counted per drive and does not move when the team grows, and the rate on the card is per person before any of that applies.

Every figure below was read on 1 September 2026 from Descript's own pricing page, help centre and team pages. Its pricing headline reads "Plans for Every Creator", and the pages underneath it are written for somebody else.

What Descript is, and what a seat buys

Descript's about page describes the product in one line: it says "Descript is a video editing app that does it all", and adds that the app "makes it easy for anyone to record, edit, and share any video". The mechanism underneath that description is the thing being priced. Descript transcribes a recording, then edits the video when you edit the transcript, so cutting a sentence out of a document cuts it out of the footage.

That matters to the price because of who it puts on the tool. A team buying a timeline editor buys it for the one person who can drive a timeline. A team buying text based editing is buying the possibility that anybody can make the edit, and the vendor sells it that way: its sales enablement page argues that text based editing "makes everybody on your team a video editor". That is why the seat count is the live question.

The seat has two shapes and only one is charged. Descript's drive membership documentation splits members into an Editor, labelled a paid seat, and a Viewer, labelled a free seat. Its permission table sets the boundary: Viewers can view and comment on projects in the drive, and cannot create, edit, export or use any feature that consumes the metered allowances. Free viewers are not unique to this vendor and the same design decides what Avoma costs, where the unit is a recorder seat rather than a head. What differs here is what the paid seat does to the meters.

The published ladder, and which billing state it shows

Descript's pricing page has a Monthly and an Annual control with the line "Saving up to 35% over monthly plan" beneath it, and it opens on Annual. In the served markup the Monthly button holds an aria pressed value of false and the Annual button holds true, so the first figure a visitor sees on each card is the annual billed rate expressed per month.

Both states ship in the same document, and the plan payload behind the cards names them rather than leaving them to be inferred. Hobbyist has an annual amount of 16 and a monthly amount of 24, Creator 24 and 35, Business 50 and 65, and Enterprise no amount and a price label of Custom. Free is zero in both states. Every figure is per person per month, and the seat line on the top card reads "Scale to a team of 5 (billed separately)".

Comparing each pair gives a third off Hobbyist, just under a third off Creator and just under a quarter off Business, so the advertised ceiling belongs to the smallest plan rather than to the team tier. That arithmetic is ours, from the vendor's published figures.

One absence matters to a reader on a non American connection. A dollar glyph is the only currency marking anywhere in the served bytes of that pricing page: a scan returns zero occurrences of USD, zero of any other ISO code and no structured price object of any kind.

A reading trap sits in the same markup. The symbol and the numeral are separate elements, so a search for the concatenated string finds nothing on a fully priced page, and both billing states render at once, so a naive read pairs two figures that are one plan in two states. The plan object is the surface to read, which is the lesson Wistia's annual default pricing teaches from the other direction, where the monthly figures are absent entirely rather than merely adjacent.

Three allowances, two denominators

No ranked page explains this part. Descript meters three things and they are not counted against the same unit. The comparison table on the pricing page labels its first row "Media minutes (per editor)" and its AI row "AI credits (per editor)". The help centre is explicit about what per editor does: it states that the total allocated to a drive "depends on how many Editor seats are on the subscription", that "Each seat adds to the shared pool of Media minutes and AI Credits", and that "Any Editor can use these resources". So a paid seat buys a person and a quantity at the same time, and the quantity lands in one pool the whole drive draws down.

The published monthly allowances per editor are 60 media minutes and 100 one time AI credits on Free, 600 minutes and 400 credits on Hobbyist, 1,800 minutes and 800 credits on Creator, and 2,400 minutes and 1,500 credits on Business.

The third meter is counted differently. The same table labels it "Recording session hours (per drive)" and publishes 2 hours on Free, then 5, 15 and 25 hours a month. Per drive, not per editor. On those figures a Business drive growing from one Editor to five takes its media minutes from 2,400 to 12,000 a month and its AI credits from 1,500 to 7,500, arithmetic ours, while its remote recording allowance stays at 25 hours.

That asymmetry points the wrong way for the team most likely to buy this. The allowance that does not scale is the one a distributed team uses to record together, and an extra seat makes it scarcer per person.

Media minutesCounted per Editor seat

• Charged when media is uploaded or recorded
• A still image counts as one second
• Each seat adds its allowance to one shared drive pool
• Any Editor on the drive can spend the pool
• Unused minutes do not roll over

AI creditsCounted per Editor seat

• Spent on generative and AI editing features
• Also spent by chatting to the assistant with no tool run
• Each seat adds its allowance to the same shared pool
• Two cost shapes, one predictable and one not
• Unused credits do not roll over

Recording session hoursCounted per DRIVE

• Total remote recording hours per drive per month
• Does not increase when an Editor seat is added
• A session counts once, not once per participant
• Room participant ceiling is the same on every tier
• The allowance a growing team dilutes

The top up card, and the arithmetic it makes possible

Most vendors in this category answer the overage question with a sentence. Descript answers it with a rate card, and per unit prices at three bundle sizes let a buyer compute.

Its help centre prices AI credits at 35.00 dollars for 350 credits, 80.00 for 1,000 and 200.00 for 4,000, printing the per credit rate beside each at 10 cents, 8 cents and 5 cents. Media minutes are sold in hour bundles at 25.00 dollars for 5 hours, 80.00 for 20 and 150.00 for 50, with per hour rates of 5.00, 4.00 and 3.00 dollars. The rule behind those unit rates is stated in the vendor's own words: "Larger bundles bring the per-unit price down."

Three conditions change what that card is worth. Top ups are available only on the Creator and Business plans, which the pricing table confirms by marking both top up rows as not included on Free and Hobbyist. They are shared across the drive. And they behave in the opposite direction to the allowance on expiry: the monthly pool does not roll over, while a purchased top up lasts twelve months from purchase and is drawn down only after the monthly allowance is exhausted.

The vendor also publishes its own advice: buy a top up for a temporary spike, upgrade if you run out every month. The card bears that out, because a Business seat at the annual rate buys 2,400 media minutes and 1,500 AI credits a month and the same volume bought as top ups costs several times the seat.

The meter you cannot budget

Media minutes are a stopwatch. Upload an hour of footage and an hour is gone, and the help centre confirms the count is the length of the media rather than a function of what you do to it.

AI credits are not a stopwatch, and the vendor says so plainly. Its help centre splits AI cost in two. Applying a tool by hand is described as a predictable cost that scales with the size of the job, and running the same input twice charges the same amount both times. Working through the AI assistant is different, and the same article says those costs are "non-deterministic and depend on what the AI ends up doing", with "no fixed price per action".

Two consequences follow for anyone forecasting a bill. When the assistant runs a tool on your behalf you are billed twice over, for the assistant working out what to do and again for "The tool itself (doing the actual work)", so an assisted edit costs more than the same edit performed directly. And talking to the assistant spends credits on its own, because "each message still uses a few AI credits" even when no specific tool is applied.

Two ceilings limit the damage. Studio Sound and Remove Filler Words carry a stated maximum of 30 credits per file per tool application however long the file is, and the model picker makes the more expensive generative models a choice rather than a default. Neither ceiling applies to the assistant.

1. Step 1Pick the tier and the billing state

   The rate is per person per month, and the page opens on the annual state

2. Step 2Count the Editors, not the team

   Viewers are free, so the paid seat count is the number of people who actually edit

3. Step 3Multiply two of the three allowances

   Media minutes and AI credits scale with seats into one shared pool; remote recording hours do not

4. Step 4Add top ups where the pool runs dry

   Available on the two upper plans only, shared across the drive, and valid for twelve months

The terms a procurement review will ask about

The commercial mechanics sit in the help centre rather than on the pricing page, and three of them decide more than the tier does.

Billing runs upfront at the start of the cycle, and the cycle date is set by when the drive subscription was created rather than by the last payment. Upgrades take effect immediately and are prorated with a credit for unused time, and the vendor publishes its own worked example: one Editor on a Business drive at the monthly rate who adds a second Editor halfway through the month pays half a seat immediately and two full seats at the next renewal. Downgrades and cancellations wait for the end of the cycle and are not prorated.

The vendor's own pages then disagree about one mechanic, and the honest thing is to report the disagreement rather than pick a winner. The billing overview and the guide to changing a billing cycle both state that switching from monthly to annual takes effect immediately, and the overview attaches a prorated credit. The refund policy states that "Changing your billing cycle partway through the subscription period is also not prorated" and that it takes place at the end of the current cycle. Two surfaces say immediate and prorated, one says deferred and not, and all three were served the same day.

The third mechanic is the one to check before anybody signs. By default any Editor on the drive can invite another person as an Editor, and the role documentation states that upgrading a Viewer to an Editor adds a paid seat unless one is already free. Manual approval of Editor invitations exists but is a setting somebody has to turn on. The refund policy gives a drive owner seven days from the invoice date to reverse an unwanted Editor, against a general plan refund window of 48 hours. The default configuration lets a seat be added by somebody who does not own the budget, and the remedy has a clock on it.

Before the first paid seat

• ✓Yes: You counted Editors rather than headcount, and put everyone who only reviews on a free Viewer seat
• ✓Yes: You know which billing state your quoted figure belongs to, because both render into one page
• ✓Yes: You checked the remote recording allowance against how often the team records together, since it does not scale with seats
• ✓Yes: Somebody turned on manual approval for Editor invitations before the drive was opened up
• ✓Yes: You asked what happens to a mid cycle switch from monthly to annual, because the vendor's own pages disagree
• ✕No: You are budgeting the assistant's usage as a fixed monthly figure
• ✕No: You are treating an unused allowance as something that carries into next month

Enterprise is quoted rather than published, and the vendor's page states what the tier is for rather than what it costs: single sign on through any identity provider using SAML 2.0, automated provisioning through SCIM, drive admins, private workspaces, custom retention and an option to opt out of training, a dedicated customer success manager, and a SOC 2 Type II report available through a trust centre on request. Its summary of Enterprise seat mechanics repeats the pooling rule in its own words, "All usage is pooled across Editor seats for the entire Enterprise Drive", and puts Viewer seats at free and unlimited. The only discounted plan the vendor offers is a nonprofit and education rate on the Hobbyist feature set, which its own page says suits individual creators.

Where this sits in an outbound programme

A video tool lands on a go to market budget because the output goes into a channel. Descript's sales page is written for exactly that: video attached to email, a personalised segment swapped in rather than a rerecording, and a shareable link where, in its own words, "Video view counts will tell you whether they actually watched". Whether the content earns the attention the outreach then spends is the prior question, set out in content led outbound, and the enablement side of the argument sits in sales enablement tools.

Two boundaries are worth naming. Descript captures and edits; it does not analyse a live sales conversation, which is a different category with a different buying question set out in conversation intelligence. And a video tool changes what a message looks like rather than how many of them find a real buyer. Our own position is one message per campaign, sent because something happened rather than because days elapsed, so a recorded video is an angle on a single send rather than an extra touch in a sequence.

If the constraint is the number of qualified conversations rather than the polish of the ones you have, see what a first campaign produces before buying the tooling around one.

The short version

Descript prints a complete rate card. Free is zero, Hobbyist is 16 dollars per person per month billed annually or 24 billed monthly, Creator is 24 or 35, Business is 50 or 65, and Enterprise is on request. That ladder opens in its annual mode, renders both billing modes at once, and names no currency beyond the symbol.

What the card does not show is the denominator. Media minutes and AI credits are counted per Editor seat and pooled into one shared drive, so a seat buys a person and a quantity together, while remote recording hours are counted per drive and stay flat as the team grows. Viewers are free, so the seat count to price is the number of people who actually edit.

Neither monthly allowance rolls over, and a purchased top up does, for twelve months, on the two upper plans only. One of the two metered currencies is non deterministic by the vendor's own account, so it can be tracked but not forecast, and the defaults let any Editor add a paid Editor.

Plan rates, allowances, top up prices and subscription terms above were read from Descript's own pricing page, help centre and team pages on 1 September 2026. Vendor pricing moves. Verify current terms with the vendor before relying on them.