Loom pricing explained: plans, limits, and billing

The plan picker looks simple until you add people. A team lead may need unlimited recordings, an editor may need text-based editing, and finance may be buying through Atlassian rather than Loom.com. Suddenly the question is not just "How much is Loom?" It is which people need paid seats, which limits matter, and which billing system will issue the invoice.

This guide separates those decisions. Prices and plan details were checked against Loom and Atlassian on September 15, 2026. They can change, so the source links are included wherever a current price or billing rule matters.

Quick answer: how much does Loom cost?

Loom has four main plans. Starter is $0. Business is listed at $18 per user per month. Business + AI is listed at $24 per user per month. Enterprise uses custom pricing. Loom says annual billing can save 17%. Those figures were checked September 15, 2026; confirm them on the current Loom pricing page before buying.

Starter allows 25 recordings per person and five-minute screen recordings. Business removes the video-count and recording-time limits and adds basic editing and brand controls. Business + AI adds automatic enhancement, advanced and text-based editing, video-to-text workflows, variables, meeting notes and recaps, and admin insights. Enterprise adds organization-level security and administration, including Atlassian Guard capabilities.

• Choose Starter for a small, low-volume trial where five-minute recordings are enough.
• Choose Business when the binding constraint is recording volume or length, not AI.
• Choose Business + AI when the team will use AI editing, written outputs, or meeting follow-up often enough to justify the higher seat cost.
• Talk to Enterprise sales when SSO, SCIM, audit logs, an uptime commitment, or centralized security review is required.

Loom plan comparison at a glance

This table reflects the public Loom pricing page and Atlassian Loom pricing page checked September 15, 2026. Prices are changeable facts, not permanent product specifications. "Unlimited" below refers only to the usage item named in that cell.

Start with the plan, seat, limit, and billing problem

A useful Loom estimate has four inputs. First is the plan: Starter, Business, Business + AI, or Enterprise. Second is the number of people who need the paid capabilities. Third is the limit that forces an upgrade, such as a five-minute cap or the need for AI editing. Fourth is the purchase path, because Loom.com and Atlassian.com do not describe annual billing in the same way.

Do not multiply the headline price by the company headcount yet. Map the workflow first. Some people create recordings every day. Others mainly watch, comment, or occasionally capture something. The public pages use several user labels and workspace rules, so confirm which roles consume a paid seat in the checkout or quote for your chosen purchase path.

This order prevents two common mistakes: buying AI for everyone because a few people need it, or budgeting from a per-user price without checking how annual user tiers work on Atlassian.com.

What the free Loom Starter plan includes

Starter costs $0 and is meant for getting started with video communication. The current public limit is 25 recordings per person, with five minutes per screen recording. Loom also lists transcription in more than 50 languages, comments, and emoji reactions. Its pricing FAQ says all regular plans include a workspace with personal, shared, and team libraries for videos and screenshots.

The Atlassian pricing FAQ currently says a Starter workspace can include up to 10 users. Loom.com presents a different Creator Lite statement, covered below, so do not combine those two numbers into one universal limit. If team size decides whether the free plan works, confirm the rule in the signup flow you will actually use.

• Good fit: occasional status updates, short walkthroughs, and a small pilot.
• Likely blocker: a recording needs more than five minutes.
• Likely blocker: a person reaches the 25-recording allowance.
• Likely blocker: the workflow depends on Business controls or Business + AI features.

How to judge the 25-recording and five-minute limits

A limit matters only in the context of real work. Five minutes is plenty for pointing out a UI change or answering one support question. It is tight for an onboarding walkthrough, a detailed bug reproduction, or a multi-part training lesson. The 25-recording allowance may last a casual user for months and constrain a support agent much sooner.

Run a short pilot instead of debating hypotheticals. Ask several likely creators to record their normal work for two weeks. Track the number of recordings, how often anyone cuts a video short, and which features they reach for after recording. Do not manufacture shorter videos solely to remain on a free plan if that makes the explanation harder to follow.

Loom’s public pricing page states the allowance but does not, on the extracted page, explain every operational detail about how the count is enforced. If archiving, deleting, or moving videos could affect your decision, verify that behavior in Loom support documentation or with Loom before committing.

What Loom Business adds for $18 per user per month

Business is the first paid self-serve tier. At the checked date, Loom lists it at $18 per user per month. It includes unlimited videos and unlimited recording time, plus basic waveform editing, the option to remove Loom branding, and the ability to upload and download videos. See the live list on Loom.com.

This is the practical upgrade when Starter’s recording limits are the problem but the team does not need the AI bundle. "Unlimited" should be read narrowly: the page promises unlimited videos and recording time. It does not mean every feature, storage policy, integration, administrative control, or future service condition is unlimited.

Business can also make sense when the deliverable must leave Loom. Upload and download support matters if the team imports existing recordings, keeps local copies, sends a source file elsewhere, or needs an export process. Test that path with the file types and quality your team uses.

What Loom Business does not include from the AI tier

Business solves the capacity problem. Business + AI solves a different problem: the work that happens after recording. The distinction matters because a team can need unlimited recording without needing automated enhancement or video-to-text outputs on every paid seat.

On the current plan page, automatic video enhancement, advanced editing, video-to-text automation, automatic meeting recap emails, automatic meeting notes, and admin insights sit in Business + AI. Loom’s AI list also names variables, summaries, and filler-word removal. If one of those is the reason for upgrading, budget for Business + AI rather than assuming the $18 Business seat includes it.

Basic waveform editing is included in Business. Text-based and other advanced editing belong to the AI tier. That line is more useful than a vague "editing included" checkbox because it tells you whether the editor is for simple cleanup or for changing a recording through its transcript and automated tools.

What Loom Business + AI adds for $24 per user per month

Business + AI is listed at $24 per user per month as checked September 15, 2026. It includes everything in Business, then adds automatic video enhancement, advanced and text-based editing, video-to-text automation, variables, automatic meeting notes and recap emails, and admin insights. Loom describes related AI outputs such as summaries and filler-word removal on the same pricing page.

The useful buying question is not whether AI sounds helpful. It is which repeated task disappears. One team may use text-based editing to clean up every customer walkthrough. Another may turn recordings into SOPs or issue descriptions. A third may only want an occasional summary. Those usage patterns produce very different value from the same seat.

Before a broad rollout, give the AI tier to a small group and measure actual use. Count recordings edited with AI, written outputs that reached a real destination, and meetings where the notes replaced manual follow-up. A feature being available is not the same as a workflow changing.

When the extra $6 for Business + AI is worth considering

The public monthly difference between Business and Business + AI is $6 per paid user at the checked date. That comparison is useful, but it can hide a bigger decision. Multiplying the difference across every creator may be unnecessary if only a small group handles polished customer videos, writes process documentation, or owns meeting follow-up.

Start with frequency. If a person uses advanced editing or a video-to-text workflow several times a week, the upgrade has a concrete job. If they record frequently but send the first take with a quick trim, Business may cover the work. If they mostly watch, confirm whether they need a paid creator role at all.

Also check destination fit. An automatically generated output saves little if someone must rebuild it by hand in another system. Test one complete route: record, edit, generate the text, move it to the place where work happens, and have the recipient use it. Price the completed workflow, not the demo moment.

What Loom Enterprise pricing covers

Loom does not publish a fixed Enterprise price. The tier requires a sales conversation and includes everything in Business + AI. Publicly listed additions include advanced security, SSO and SCIM, a 99.95% uptime SLA, enterprise administration, and the Standard package of Atlassian Guard. Loom says Guard Standard brings enforced single sign-on, automated user provisioning, and an organization audit log.

A quote should be evaluated as more than a per-seat number. Ask which security and administration features are included, which require another Atlassian product or package, how user provisioning affects billing, what support terms apply, and whether the quote assumes annual commitment. The Atlassian page says Enterprise is available only on annual subscriptions.

Do not infer regulatory coverage, data residency, retention, or legal terms from the phrase "enterprise-grade." Those are specific requirements. Put each one in the procurement checklist and require the contract or current product documentation to answer it.

Monthly versus annual Loom billing

Both current pricing sources say annual billing can save 17%. Monthly billing reduces commitment and makes a pilot easier. Annual billing lowers the stated cost when the team size and plan fit are stable. Confirm the final total in checkout because the displayed monthly rate, annual invoice, taxes, user tiers, and contract terms are separate pieces of the purchase.

The Atlassian pricing FAQ says monthly subscriptions are charged for the next month based on the exact number of Loom users. Annual subscriptions are charged by the user tier that most closely matches the user count. The Loom.com FAQ says Loom.com annual subscriptions are charged by the distinct number of paid users and billed annually.

That difference can affect the estimate. A team buying annually through Atlassian should use the calculator for its expected user count rather than multiplying a headline per-user rate. A team buying on Loom.com should confirm who counts as a distinct paid user during the term.

Loom.com versus Atlassian.com billing

Loom is part of Atlassian, but the two purchase paths are still not described as identical. Loom’s own FAQ says the systems are being integrated and that some differences are temporary. It currently directs buyers to compare Loom.com with Atlassian.com before purchasing.

According to that FAQ, purchases through Atlassian.com have access to Atlassian’s Administration hub for organizations, apps, users, and billing; Loom recording entry points inside Confluence and Jira; and SSO/SCIM provisioning through Atlassian Guard. The annual billing model also differs: distinct paid users on Loom.com versus user tiers on Atlassian.com.

This does not mean one route is universally cheaper or better. The public pages do not provide enough information to make that claim for every team size and contract. Use the route that matches your administration needs, enter the same user count in both available flows, and compare the actual quote, included controls, payment method, and renewal terms.

Why the Starter team limit needs a channel check

The public FAQs currently show a mismatch worth noticing. The Atlassian page says Starter supports up to 10 users in a team workspace. The Loom.com page says Starter can add up to 50 Creator Lite members for free. Those are not interchangeable statements: one refers to users in the Atlassian purchase flow, while the other names a particular Loom role.

Do not choose the more convenient number and apply it everywhere. If a free team workspace is part of the plan, start signup through the intended purchasing route and verify the roles available there. Ask what Creator Lite members can create, what triggers a paid Creator seat, and whether an existing Atlassian organization changes the setup.

This article uses the Atlassian FAQ’s up-to-10-user figure in the plan table because that is the stated team limit in that source. The Loom.com Creator Lite statement is preserved here so buyers can see the current discrepancy instead of getting a false single answer.

How Loom seat costs grow across a team

For a simple monthly self-serve estimate, multiply the number of paid users by the listed monthly rate for the selected tier. Keep Business and Business + AI users separate if the chosen billing setup allows a mixed arrangement. Do not assume mixed tiers are supported inside one workspace until the checkout or sales team confirms it.

Then add the questions the multiplication misses. Will contractors need creator access? Are there seasonal hires? Who owns deactivating unused accounts? Does annual Atlassian tiering leave paid capacity above the current headcount? Will identity provisioning automatically add people who should only watch?

The best seat audit uses activity and job requirements together. A dormant account may be removable. An infrequent creator may still need access for a critical monthly process. A frequent viewer may not need creator capabilities. Document the role rule before procurement so the estimate can be repeated at renewal.

A practical Loom cost calculation

Build the estimate in rows, not as one headcount number. Create rows for occasional creators who fit Starter, regular creators who need Business, people who need Business + AI, and administrators or security stakeholders involved in Enterprise. For each paid row, record seat count, billing route, monthly or annual term, and the feature that justifies the tier.

Next, model a base case and a growth case. The base case uses current paid users. The growth case includes expected hires and contractors through renewal. If purchasing annually through Atlassian, run both counts through its calculator because a user-tier boundary may change the result. If purchasing through Loom.com, confirm how distinct paid users are counted over the annual term.

Finish with a reconciliation date. Pricing pages change, people change roles, and unused seats accumulate quietly. Review the roster before renewal and after reorganizations. The calculation is complete when finance can trace every paid group to a requirement, not when the spreadsheet happens to equal the checkout total.

1. Count people by the capability they need, not by total workspace membership.
2. Choose the purchase path and billing term.
3. Apply the current public rate or Enterprise quote.
4. Check annual tier boundaries and role definitions.
5. Model expected headcount at renewal.
6. Set an owner and date for the next seat review.

Which Loom plan fits a larger organization?

Larger organizations usually reach a governance requirement before they reach a recording requirement. Identity provisioning, enforced SSO, audit logs, centralized administration, uptime commitments, and procurement terms move the conversation to Enterprise even if creators would otherwise be satisfied with Business + AI.

Bring security, IT, legal, and the workflow owner into the evaluation early. Ask Loom to map each requirement to the exact plan and contract language. Confirm how Atlassian Guard is included, who administers it, and whether the organization already has overlapping Atlassian controls.

Run a content-lifecycle review too. Decide who owns recordings when an employee leaves, how long videos should remain available, how exports work, and which workspaces can share externally. The pricing page is the start of that conversation, not evidence that every policy requirement is covered.

Loom pricing versus Zight: compare the workflow, not just the seat

Loom and Zight both support screen recording, but the plan decision should follow the communication job. For a feature-by-feature review, use the Zight versus Loom comparison. If you are still building a shortlist, the best Loom alternatives guide covers several recording approaches.

Zight’s current lineup includes a free Share plan, paid Create and Collaborate plans, and a Scale plan for organizations. The free plan includes recording, screenshots, GIFs, and five Video Requests per month, with five-minute recordings. Unlimited uploads and recording time start with Create. Collaborate adds team-oriented capabilities such as unlimited AI actions, custom branding, and more Video Requests. Scale adds organization controls and custom request volume. Check current Zight plans rather than relying on a hard price in an article.

The structural difference is inbound context. A Zight Video Request lets someone record and return their screen without an account or install. Request Links can also collect screenshots, files, and diagnostic context. That matters for support, IT, product, and engineering teams that spend as much time gathering evidence as they do sending explanations. If all you need is outbound recording, compare the recording and editing experience directly.

Common Loom pricing mistakes to avoid

A clean purchase memo should state the source date, plan, number and type of users, billing route, billing term, forcing feature, and assumptions that still need confirmation. That gives procurement something testable and gives the next renewal owner a record of why the plan was chosen.

• Quoting an old price without a checked date. Loom prices and packaging can change.
• Treating the displayed monthly figure as the final annual invoice.
• Multiplying by total headcount before determining who needs a paid creator seat.
• Assuming Loom.com and Atlassian.com use the same annual billing method.
• Applying the Atlassian Starter user limit to a Loom.com Creator Lite workspace, or vice versa.
• Choosing Business for an AI feature that is listed under Business + AI.
• Reading "unlimited recording" as "everything is unlimited."
• Buying Enterprise based on a security label without checking each requirement.
• Evaluating the recorder but not the export, recipient, administration, and renewal workflows.

Questions to ask before buying Loom

Use a real recording during the trial. Make it with the screen recorder, edit it the way the team normally would, send it to a real recipient, and verify the outcome. A pricing page can tell you what is included. Only the completed task tells you whether the plan fits.

1. Which people need to create, and which only need to watch or comment?
2. Will any normal recording exceed five minutes or the Starter recording allowance?
3. Is basic waveform editing enough, or does the work require text-based and automated editing?
4. Which AI outputs will enter a real workflow, and how often?
5. Are we purchasing through Loom.com or Atlassian.com?
6. How will monthly exact-user billing or annual user-tier billing apply to our roster?
7. Which roles count as paid users in our chosen purchase path?
8. Do we require SSO, SCIM, audit logs, an SLA, or other Enterprise terms?
9. What happens to videos, links, and ownership when a person leaves?
10. Who will review seats and plan fit before renewal?

Loom pricing FAQs

These answers use the public Loom and Atlassian pricing pages checked September 15, 2026. Recheck the linked sources for a purchase made after that date.