1. LandOffer
  2. Blog
  3. All articles
  4. Fireflies.ai Review: Separate Transcription, Storage, Upload Limits, and AI Credits

AI at Work

Fireflies.ai Review: Separate Transcription, Storage, Upload Limits, and AI Credits

Separate retained meeting storage from monthly uploads, single-file limits and advanced AI credits. A complete six-month capacity ledger and import exception case show when a storage upgrade changes the decision.

10 min readLandOffer team

Fireflies.ai is worth evaluating when you need a searchable meeting archive and can match its plan to your actual capture and retention requirements. Compare five separate resources: transcription entitlement, retained storage, monthly import processing, individual file limits and advanced AI credits. Paying for unlimited transcription does not make every resource unlimited, and upgrading storage does not remove an uploaded file's duration limit.

This review from LandOffer.ai checked official public documentation on October 27, 2026. It uses a completed fictional capacity ledger and two contrasting delivery choices from the same synthetic meeting packet. No Fireflies account, bot, recording, upload, integration, credit purchase or billing setting was tested or changed. The calculations are planning arithmetic, not evidence of accuracy, reliability or time saved.

An acoustic archivist separates stored cylinders, an incoming tray and loose tokens into different physical resources.

Read the resources separately

Fireflies' transcription-credit guide distinguishes its Free signup allowances from paid unlimited transcription credits. It also describes Auto-join-dependent unlimited Free transcription, with summary allowances remaining separate, and notes an account-cohort boundary beginning September 1, 2026. Do not assume an older account and a new website signup receive identical terms. Turning on broad calendar capture also requires an approved meeting policy; a larger allowance is not permission to record people.

Storage documentation measures retained meeting minutes, including live captures and imported files. Pro provides 8,000 minutes per user pooled across the team; Business and Enterprise list unlimited storage. That is retained stock, not a new allowance every month. The guide says new meetings can still be captured at the cap, but older material must be removed to access new meetings.

For Free teams, the public pages disagree: pricing says 400 minutes per team, while storage help describes per-user allocation and pooling. This review does not resolve that discrepancy by multiplying Free seats. A Free team buying decision needs the actual workspace entitlement confirmed.

The upload guide separately lists a 150-minute maximum per uploaded file, 500 MB for audio, and video limits of 100 MB on Free or 2 GB on paid plans. MP3, M4A, WAV, MP4 and WEBM are supported examples. A paid video-size allowance does not increase the 150-minute duration ceiling.

A live recording's limit is another question. The pricing comparison has recording-duration rows; do not substitute the upload ceiling for the permitted length of a bot recording. Check the actual plan and capture method for a long workshop. A file prepared after that workshop remains an upload, even if its subject was a meeting.

Monthly processing does not replace retention capacity

The rate-limit guide describes paid import processing at 3,000 minutes per user, per source, per calendar month, with a 150,000-minute team ceiling per source. Dashboard uploads, integration imports and past-meeting transcription belong in the relevant source ledger. Live notetaker meetings, supported Chrome-extension capture and mobile recordings are treated differently.

Keep an upload's duration, source and intended processing month together. Moving an old file into a new month changes the processing budget; its original meeting date does not create a fresh allowance. Unused processing minutes do not roll forward. API request limits are another control, so a minute calculation alone does not prove an integration can run as requested.

Overage billing is unresolved in the public documentation. The current rate-limit article says no overage charge in its main explanation and FAQ, but its large-team example mentions $0.01 per excess minute. The separate upload and integration guide also lists that charge. Do not treat either “free excess” or a calculated extra-dollar amount as a confirmed quote. Ask the billing owner to resolve the applicable account terms before exceeding the allowance.

Build the purchase case around work that fits without relying on that uncertain boundary. A storage upgrade can be useful while leaving the import allowance unchanged. Conversely, a small import batch can fit this month's processing allowance while pushing the retained archive beyond its storage cap.

Worked asset: a complete retained-stock and incoming-flow ledger

The following is an authored fictional example, not a Fireflies workspace inspection. The Oriole documentation team has three paid Pro users. Their existing approved archive contains 18,600 minutes of invented training discussions. For November 2026, the first of six planned months through April 2027, they want to import eighteen 100-minute audio recordings and retain twelve new 50-minute live meetings. Each synthetic audio file would be an MP3 of 120 MB.

Mika owns the inventory, Sol owns the retention review and Dev handles the purchasing proposal. Nobody has approved deletion of the existing archive. The team needs six months of comparable access, not merely a successful first upload. These are requirements supplied for the example, not claims about any organization's retention obligations.

Ledger line Completed calculation Meaning for the proposal
Pro pooled retained capacity 3 × 8,000 = 24,000 minutes Shared total, not 24,000 new minutes each month
Already retained 18,600 minutes 5,400 minutes initially available
Proposed imports 18 × 100 = 1,800 minutes Dashboard-import source, this planning month
Proposed live meetings 12 × 50 = 600 minutes Adds storage even though this capture path is outside the listed upload-minute limit
End of first month 18,600 + 1,800 + 600 = 21,000 minutes 3,000 minutes of storage remain
End of second equal month 21,000 + 2,400 = 23,400 minutes Only 600 minutes remain
End of third equal month 23,400 + 2,400 = 25,800 minutes Exceeds Pro capacity by 1,800 minutes
End of sixth equal month 18,600 + 6 × 2,400 = 33,000 minutes Exceeds the existing Pro pool by 9,000 minutes

For the three-seat paid team, the documented dashboard-source planning allowance is 9,000 minutes per month. The proposed 1,800 import minutes sit 7,200 below that allowance. Each 100-minute, 120 MB audio file also sits below the documented individual audio limits. Those are independent checks; the unused 7,200 processing minutes cannot be converted into retained storage. Buying another month of the same plan does not erase the accumulated archive.

The completed finding is that this steady workload fits the first two storage snapshots but not the third. Sol rejects “delete something when it fills” as an approved retention plan. She records the unresolved decision for Dev: compare Business against a written retention alternative by November 6, before the planned third month begins. Any removal alternative must identify which material can leave Fireflies, where its approved preserved copy will live and who can verify access. No such removal policy is approved yet. No records are deleted in this example.

At 2,400 new minutes per month, the remaining 600 minutes after month two cover only that amount of additional retained material. They do not establish a precise date when access changes: actual meetings arrive unevenly. Mika therefore owns a weekly retained-minute check during the next month rather than announcing an invented failure date. The calculation predicts capacity under stated inputs; it does not demonstrate an actual access restriction.

This ledger also exposes duplicate imports. If an existing recording is accidentally submitted again, the arithmetic needs to account for the additional processed and retained material until the actual product's treatment is known. The calculation does not assume automatic deduplication or unlimited replacement attempts.

A curator compares a long incoming audio reel with a small gauge while another reel remains safely on the archive shelf.

Worked asset: choose the live and imported-file paths

Use the same Oriole packet for a completed procurement decision. The ordinary 50-minute live calls and 100-minute MP3 imports remain in scope. A newly requested 175-minute training recording, saved as a 700 MB MP4, is an additional exception. The team also wants standard summaries and occasional questions about individual processed meetings; it has not approved custom AI automations.

Requirement Documented fit or boundary Completed decision and owner
First month's ordinary packet 21,000 retained minutes within the three-seat Pro pool; imports below the dashboard allowance Mika keeps Pro as the short-term candidate, conditional on the actual account entitlement
Preserve all six months 33,000 planned minutes exceed the 24,000 Pro pool Dev requests a Business storage comparison; no deletion substituted for the requirement
Import the 175-minute MP4 Paid size allowance accommodates 700 MB, but the 150-minute duration ceiling fails Mika excludes this file from the accepted import batch; it is not marked uploaded
Capture future eligible calls live The documented live path is outside this upload-minute allowance Sol still requires participant and organization approval; no bot invitation occurs
Ask about a processed meeting Paid Notepad AskFred has a specific no-AI-credit boundary Evaluate that exact surface before adding a paid AI package
Custom sections or live AI assistance Advanced credit-metered features differ from standard transcription Dev leaves these deferred, with no new credit subscription authorized

The longer MP4 does not become eligible simply because Business offers unlimited retained storage. Mika's completed exception record reads: “175 minutes exceeds the published upload duration; original preserved; no import attempted; request an approved alternative.” If the content owner authorizes segmentation, the team must retain continuity and verify every resulting segment. This review has neither divided a file nor tested reconstruction, and it does not promise segmentation will preserve meaning or satisfy policy.

For the six-month retention requirement, Business is the stronger candidate on documented capacity. For a genuinely short project with an approved exit and preservation plan, staying on Pro may be sufficient. The same ordinary imports fit both scenarios, so the upgrade argument rests on required retained history, not an invented monthly transcription shortage.

Using the public annual-billing references, three Pro seats at $10 per seat monthly equivalent total $360 annually. Three Business seats at $19 total $684, a $324 annual difference. These are calculations from the pricing page, not a checkout quote; taxes, account-specific offers and added services are unverified. A short project should compare its actual billing commitment. Dividing an annual purchase by two project months can hide the cash commitment a budget owner must authorize.

Put AI credits in their own purchasing line

The AI-credit guide explicitly separates standard transcription from advanced feature usage. Its included credits are one-time team pools: Pro 20, Business 30 and Enterprise 50. They do not multiply with teammates or stack with an earlier plan allocation. Purchased allowances renew separately; dynamic usage means a balance cannot be converted into a guaranteed number of requests.

Oriole's three Pro seats therefore do not create 60 included AI credits. Moving to Business would replace the starting pool with 30, not add 30 to 20. Neither change proves that six months of custom prompts are funded. The team keeps credit-dependent automation outside its accepted scope until actual requirements and account controls are reviewed. Fireflies also documents automatic billing for paid accounts when the included pool runs out: a first AI-credit subscription at $5 per month for 50 credits, or an upgrade to the next tier for an existing credit subscriber. Free users instead meet a paywall. Dev must verify and, if required, have the authorized admin change those controls before relying on a no-add-on budget; excluding a feature from this written plan does not disable an account's automatic charge.

The meeting-specific AskFred guide says paid users can ask questions inside a processed meeting's Notepad without consuming AI credits. Live Assist, Sales Assist, Global AskFred and AI Skills have different metering boundaries. Ordinary summary templates and custom summary sections are also distinct. “AskFred included” is too broad to use as the cost model.

The Personal Assistant guide, freshly updated when checked, describes Daily Digest and Meeting Prep as enabled by default and credit-consuming, with a gradual interface rollout. Tasks is documented as free. Oriole records a requirement to inspect the actual workspace controls with its authorized admin before relying on those defaults; no setting is changed here. Its proposal does not authorize auto-subscription, automatic credit upgrades or new AI automations.

Choose Fireflies when its documented capture paths, archive capacity and review workflow fit the work. Keep the unresolved Free pooling and overage terms visible, preserve original recordings, and price advanced AI separately. LandOffer.ai publishes related workplace guidance; the immediate next step is an account-specific entitlement review and an approved small sample, not an unapproved recording or subscription change.

Sources and Further Reading