Included storage comes from the current plan
Storage is shared across the studio workspace. It is not a separate allowance for each job, client, or studio user.
- Starter: 200 GB
- Team: 1 TB
- Scale: 3 TB
Use the current Pricing page as the public source for plan allowances. Do not maintain another independent table in this article.
The workspace can also include a current recurring storage pack or a grandfathered legacy storage entitlement. The storage summary should show each source separately.
A missing or inactive subscription is not unlimited storage. The product should show the current account state and whether new uploads are allowed.
Workspace storage is the retained file total used for plan enforcement
Lenso records storage for files the workspace keeps as part of the current product. The counted total can include files uploaded by studio users or clients.
The number is not the raw size of every object in the underlying storage bucket. Generated previews, temporary archives, and other product-managed files can follow a different accounting rule.
The accounting policy must be the same in upload checks, deletion, reconciliation, the storage API, and this Help page.
What counts toward the limit
The current active version of each creative counts, together with brief, reference, message, and other counted attachments. Earlier creative versions can remain in history under the current product policy without increasing the creative quota. This policy can change only with customer notice and synchronized code, Pricing, and Help updates.
What does not count under the recommended policy
- Generated watermarked previews
- Generated client-web derivatives
- Generated thumbnails
- Temporary delivery ZIPs
- Failed or abandoned upload sessions
- Objects already removed from the canonical product record
- Internal operational copies that the product explicitly excludes
A file is not excluded merely because it is archived, old, or difficult to find.
How Lenso measures storage
The current accounting rounds each counted file up to a whole megabyte. A very small file can therefore count as 1 MB.
The displayed total can be slightly higher than a sum reported by an operating system or spreadsheet.
The product displays MB, GB, or TB at a readable scale while preserving the exact current total for enforcement.
Usage updates after a file is finalized or removed. Bulk processing and reconciliation can take a short time to appear.
The quota total should come from the canonical product inventory, not a raw bucket total that also contains generated and temporary objects.
Read the storage summary
- Current plan
- Base included storage
- Recurring storage packs
- Grandfathered legacy storage, when any
- Total current limit
- Counted storage used
- Reserved upload capacity, when uploads are in progress
- Storage available
- Percentage used
- Last calculated time
- Current upload state
Uploads available
The workspace has active write access and the next file can fit inside the current remaining capacity.
Approaching the limit
The workspace still has capacity. Review usage before a large upload.
At the limit
Current counted or reserved usage equals the limit. New uploads that would increase counted storage are paused until capacity becomes available.
A replacement that does not increase counted storage can continue under the current upload policy.
Over the limit
Current counted usage is above the limit, commonly after a plan downgrade, storage-pack removal, or accounting correction. Existing files remain while new uploads are paused.
Subscription action required
The workspace does not currently have write access under the subscription policy. This is not unlimited storage.
Show state in visible text. Do not rely on bar color alone.
What happens at or above the limit
- New uploads pause
- A current upload that does not fit is rejected before it is finalized
- Existing job records remain
- Existing retained files are not deleted merely because of quota
- Existing client review can continue for files already available, subject to account and access policy
- Existing downloads can continue under the current subscription, release, retention, and security rules
- Uploads resume after enough capacity is available
Over quota alone does not define account retention, cancellation, legal hold, or final-file access. Those rules are separate.
Lenso must reserve or atomically check capacity so simultaneous uploads cannot both consume the same remaining space.
Free storage by removing files the studio no longer needs
Confirm that the file is not the current approved final, a required source, the only retained version, a client reference, an accepted exception record, or evidence needed under the client agreement.
Deleting the current creative version can promote an older retained version into the counted total. When that promoted version is larger, counted usage can increase even though a file was removed.
- Delete an unused creative or retained version under the current file controls
- Remove a brief or reference attachment that is no longer needed
- Remove a message attachment when the current product supports that action
- Remove an unneeded client upload
- Clear failed or abandoned uploads through the current product cleanup
Archiving a job changes where it appears. It does not free storage while the files remain retained.
Deleting a file from Lenso can affect project history and client access. It is not the same as hiding it from a view.
Do not assume high usage is caused by duplicates. Review the actual retained categories.
When the product exposes a storage breakdown, use it to identify the category before deleting.
Add capacity
The workspace Owner can review the current plans and move to a plan with more included storage.
When the current Billing experience offers a recurring storage pack, the Owner can add capacity without changing the base plan.
Storage-pack availability, size, price, proration, quantity, and removal behavior come from the current verified Stripe configuration.
If Lenso cannot verify the configured storage-pack price, the product must show the pack as unavailable rather than display a fallback price.
An Admin or Member can view usage and help remove files they are allowed to manage. They cannot change the Lenso plan or storage add-on.
What happens when the limit becomes lower
A plan downgrade or storage-pack removal can leave the workspace at or above the new limit.
- Existing files are not removed automatically
- New uploads pause when they do not fit
- The Owner can restore capacity by changing plan or adding an available pack
- The studio can remove counted files
- The storage summary shows the new base and extra capacity separately
The current Billing flow should show when the lower limit takes effect before the Owner confirms the change.
Legacy storage entitlements remain visible as legacy capacity. They are not sold through a second hidden checkout path.
Archiving, deleting, and retaining files are different actions
Archiving a job removes it from the normal active-job view. It does not remove retained files or reduce quota unless the current product explicitly says otherwise.
Deleting a file removes the selected product record and storage object under the current cleanup path. The quota change should be idempotent and reflected after processing.
When the product supports permanent job deletion, every counted child file and attachment must be removed through the canonical accounting service.
Subscription ending, account deletion, and privacy deletion follow separate retention and recovery rules.
Do not repeat a retention period here unless it has been verified against the current product, Privacy Policy, and Terms.
Who can manage storage
All studio roles
- View the current storage summary
- See whether uploads are available
- Work with files inside jobs they are allowed to access
Owner
- Change the Lenso plan
- Open the Billing Portal
- Add or remove current storage packs
- Review platform-billing effects
- Manage workspace-wide capacity
Admin
- Manage files and jobs allowed by the current workspace policy
- Help the studio reduce usage
- Ask the Owner to change plan or storage capacity
Member
- Manage files only in jobs the Member can access and under the current file permissions
- Ask an Owner or Admin about job access
- Ask the Owner about plan or storage changes
Client
- Does not manage workspace quota
- Can upload or download only where the current job and client-access rules allow
- Does not consume a studio seat
Troubleshooting storage
The usage looks higher than expected.
Review the counted categories, retained versions, attachments, and per-file rounding. Refresh once after current processing completes. Contact Lenso when the total still does not match the canonical inventory.
The usage looks lower after reconciliation.
Treat this as an accounting defect when a counted brief, message, client upload, or retained version disappeared from the total. Real-time and reconciliation policies must match.
A deleted file still appears in usage.
Refresh after cleanup processing. When the total remains unchanged, verify the object was counted, removed once, and included in reconciliation.
Deleting the same file changed usage twice.
Treat this as an idempotency defect. A counted object can reduce quota only once.
A large upload passed the first check but failed at completion.
Another upload can have consumed the remaining capacity. The product should reserve capacity and show the current state. Retry only after capacity is available.
The workspace shows unlimited storage without an active plan.
Treat this as a state-display defect. A missing active entitlement must not appear as unlimited.
The Owner cannot add a storage pack.
Confirm that the recurring pack is configured and available for the active subscription. Do not use a fallback price. Review Pricing or Contact when the product shows unavailable.
An Admin cannot open Billing.
This is expected. Only the workspace Owner manages the Lenso subscription and storage add-ons.
Uploads stopped after a downgrade or pack removal.
The current usage is at or above the lower limit. Existing files remain. The Owner can restore capacity, or the studio can remove counted files.
Archiving a job did not free storage.
This is expected while the files remain retained. Archive and delete are different actions.
Existing downloads stopped while the workspace is over quota.
Over quota alone should not block existing downloads. Check the subscription, client access, release state, retention, and security policy. Contact Lenso when those states appear valid.
The displayed total is slightly higher than my local file-size sum.
Lenso rounds each counted file up to a whole megabyte under the current policy.