Scribe Pricing 2026: How Much Does Scribe Cost & Free Plan

Scribe pricing has a straightforward structure: a free tier with unlimited guides, a per-seat Pro plan for individuals, and a Pro Team plan that is cheaper per seat but requires a minimum of five. The numbers look reasonable until you calculate what a 10-person documentation team actually pays, and until you realize what problem that spend doesn't solve.

All prices below were checked against Scribe's public pricing page in August 2026 and are quoted in USD.

How much does Scribe cost? Plans and prices

Scribe offers four tiers targeting individuals, growing teams, and enterprises. Here is what each costs per seat, at both billing frequencies:

Scribe advertises annual billing as "save 20%". On the actual numbers it is closer to 29% on Pro Personal ($25 against $35) and 24% on Pro Team ($13 against $17). If you expect to use Scribe past a trial, annual is the only rate that matches the headline prices.

Scribe free vs paid: what each plan includes

Price per seat is the easy half of the question. The harder half is which tier holds the feature you actually came for, because the two that most teams need, desktop capture and PDF export, both sit behind the first paid step.

Two lines in that table decide more upgrades than the price does. Capture surface: the free plan records web apps in the browser, so anything you document in a desktop client is a paid feature. Version history: one week of history on every self-serve tier means a guide someone overwrote last month is not recoverable without an Enterprise contract.

How much is Scribe per month?

Billed monthly, Pro Personal is $35/seat and Pro Team is $17/seat, against $25 and $13 on annual billing. Monthly billing therefore adds roughly 30% to the per-seat cost across the paid tiers.

The Pro Team plan requires a minimum of five seats, which means the real entry price for a team plan is $65/month on annual billing, or $85/month billed monthly, even if only two people produce guides. That five-seat floor, not the per-seat rate, is what most small teams end up reacting to.

How much is Scribe Pro? Pro Personal vs Pro Team

"Scribe Pro" is two plans, and Scribe Pro pricing depends on which one you qualify for. Pro Personal costs $25/seat/month billed annually or $35 billed monthly, and it is the only paid option for one to four creators. Pro Team costs $13/seat/month billed annually or $17 monthly, but it starts at five seats.

The feature difference is collaboration, not capture. Both Pro plans include desktop and mobile capture, exports to PDF, HTML and Markdown, custom branding, and manual screenshot editing and redaction. Pro Team adds comments, shared team workspaces, and basic analytics on top. If you are a solo creator, Pro Personal at $300/year is the complete Pro feature set minus the collaboration layer; there is nothing capture-related you unlock by paying more.

What teams of different sizes actually pay

Scribe's per-seat pricing scales linearly. Predictable, but predictable doesn't mean cheap at scale. All figures are annual billing:

• Solo user (Pro Personal): $300/year. Reasonable for consultants or individual knowledge managers who need clean PDF exports for external delivery.
• 3-person team: $900/year on Pro Personal. Below five seats you cannot use the cheaper Team rate, so a three-person team pays the personal rate three times over rather than $468.
• 5-person team (Pro Team): $780/year. At $156/person/year this is the most cost-effective tier, and the first point at which the plan makes sense at all. You are paying for all five seats whether everyone creates guides or not.
• 10-person team (Pro Team): $1,560/year. At this size teams typically document across multiple product areas, which means more maintenance overhead when the UI changes.
• 25-person team (Pro Team): $3,900/year. At this scale, the time spent updating stale screenshots after each release starts showing up in billable hours more noticeably than the subscription does.
• 50-person team (Pro Team): $7,800/year. Worth auditing whether the model still fits before renewing.

Is Scribe free? Does Scribe cost money?

Yes, Scribe is free to use on the Basic plan, and no, you do not have to pay to create guides. Basic gives you unlimited guide creation, browser capture on any web app, and sharing by link or embed. It is one of the better free tiers in the documentation tool space and a genuine entry point rather than a gated demo.

Scribe starts costing money at three specific moments: when you need to capture a desktop or mobile app, when you need to export a guide as PDF, HTML or Markdown, and when you need the guide to carry your own branding rather than Scribe's. None of those are usage caps you grow into gradually. They are yes-or-no gates you hit on a specific day.

The free plan works well when you are documenting a stable internal process, sharing only within your organization, and evaluating whether Scribe fits your workflow. It stops working when you have customer-facing help content that has to stay accurate across releases, and that limit is not one a paid tier removes. Screenshot maintenance applies at every tier.

Scribe Enterprise pricing

Scribe does not publish Enterprise pricing. It is quote-based, and the feature set is a governance package rather than a capacity increase: SSO, Creator/Viewer/Admin roles, central user and document management, enterprise data governance, enforced automatic redaction of PII and PHI, language translations, and unlimited version history instead of one week.

Third-party comparison write-ups citing buyer reports put Enterprise quotes in the region of $18,000 per year and up, including for teams that expected something closer to the self-serve rates. Treat that as a reported range rather than a published price, but treat the shape of it as real: the jump from $13/seat to a negotiated annual contract has no published middle tier, which is what makes the step surprising when it arrives.

The practical read: if you need SSO or enforced redaction, budget for a sales cycle and an annual commitment, not for an upgrade button.

Scribe AI pricing: is the AI a separate line item?

No. Scribe does not sell AI as an add-on, a credit pack, or a metered usage tier. The AI-powered automatic capture that turns a recorded session into a written step-by-step guide is included on every plan, free tier included, and the AI workflow analysis features sit in the higher tiers as part of the seat price rather than on their own meter.

This is worth knowing because it is unusual. Many documentation and knowledge tools now price AI separately, so a $13/seat plan quietly becomes $13 plus credits. Scribe's per-seat number is the number. What you are paying for is seats for the people who create guides, not consumption.

What a Scribe subscription actually commits you to

Three properties of the subscription matter more than the sticker price when you model a year:

• Seats are for creators, not readers. Anyone who captures or edits a guide needs a paid seat. People who only read the guides do not, because guides are shared by link and embed. A 40-person support team with four people who write documentation is a four-seat purchase, subject to the five-seat floor on Pro Team.
• The five-seat floor is a floor, not a starting suggestion. You cannot buy a three-seat Pro Team plan. Below five creators, the choice is Pro Personal at $25/seat annual (no comments, no shared workspace) or paying for two seats you don't use.
• Annual billing is a prepay. The advertised $25 and $13 rates are annual-billing rates. Testing on monthly first costs about 30% more per seat while you evaluate, which is the honest price of not committing yet.

Upgrading adds seats at the same per-seat rate. The direction that hurts is downward: shrinking below five creators means leaving Pro Team rather than reducing it, and losing comments and shared workspace management on the way out.

The cost the pricing page doesn't mention

Scribe captures workflow documentation as screenshots with annotations. The process is fast: open the Chrome extension, click record, complete the workflow, and Scribe generates a step-by-step guide in seconds. The real cost shows up 30 days later when your engineering team ships a UI update.

Screenshot-based documentation goes stale every time a button label changes, a menu item moves, a form field gets renamed, or a workflow adds or removes a step. Scribe doesn't detect when this happens. Your team finds out when a customer emails support with a screenshot of the wrong button.

According to the GitLab DevSecOps Survey, 65% of software teams ship weekly releases or more frequently. For a SaaS product with 50 active guides on that cadence, documentation decay is a standing weekly maintenance task, and it doesn't appear anywhere in Scribe's pricing table.

The Stack Overflow Developer Survey consistently ranks outdated documentation among the top frustrations for technical users. That frustration scales directly with the gap between what a guide shows and what the product actually does.

When Scribe's pricing makes sense

Scribe is well-priced for documentation that stays stable: HR onboarding flows, IT setup procedures, internal SOPs for processes that change infrequently. For teams where the primary use case is documenting a stable tool rather than a rapidly shipping product, the subscription cost is justified and the maintenance overhead is low.

A well-structured documentation audit typically reveals which guides need frequent updates (product-facing, release-sensitive) and which are stable enough for a screenshot-based tool (internal process, rarely touched). Scribe is the right tool for the stable portion of that split.

When the math stops working

Scribe gets expensive relative to value when your product ships frequent UI changes that affect guide accuracy, when your team spends more time updating existing guides than creating new ones, or when you need a customer-facing Help Center with search and navigation rather than just shareable guide links.

The trigger for re-evaluation is usually one of two moments: a customer complaint about outdated instructions, or a quarterly review where guide maintenance is consuming 15-20% of a support team's week. At that point, the per-seat subscription cost is no longer the primary cost. The ownership question, who is responsible for keeping guides current and how much of their time it takes, becomes the more useful number to track.

Scribe alternatives at each price point

At $13 to $25 per seat per month, Scribe competes with tools that use different documentation approaches:

• Tango ($15/user/month annual on Pro Team, from 3 users; $22 for 1 to 2 users): Similar screenshot-based approach with interactive walkthrough features. Cheaper below five seats and it has a lower team minimum, with an identical maintenance problem. Its free plan caps you at 5 shared workflows where Scribe's is unlimited, so the two free tiers trade different limits. Full breakdown in Scribe vs Tango.
• Confluence ($6-$12/user/month): General wiki. Cheaper, but guide creation is entirely manual, with no recording capability. Different use case.
• Purpose-built Help Center platforms: Higher initial cost in some cases, but built for customer documentation with search, analytics, and in some cases automated staleness detection after releases. See HappySupport vs Scribe for that comparison.

The comparison changes when you factor in maintenance labor. A $13/seat tool that requires two hours of guide updates after every release can cost more in real dollars annually than a platform that handles those updates differently. The subscription is one line. The maintenance hours are another.

The bottom line on Scribe pricing

Scribe is fairly priced for what it does. The free tier is a genuine entry point. Pro Team at $13/seat annual is cost-effective once you are past five creators. The underlying issue isn't the price, it's the model. Screenshot-based guides require manual maintenance every time the product changes, and Scribe does nothing to detect when that maintenance is due.

For teams with customer-facing help content and weekly release cycles, the subscription cost is only part of the picture. The larger cost is the hours spent keeping guides current. HappySupport takes a different approach: guides built with the AI step-by-step recorder capture DOM and CSS structure instead of pixels, so documentation stays in sync when code ships and screenshots regenerate automatically instead of going stale. The maintenance cycle breaks rather than compounds.

If you're comparing costs, HappySupport's pricing is published, and you can see how the self-updating model works on the self-updating documentation page.