File Upload Limits

In addition to your total storage quota, your plan controls the size of an individual file upload. These limits are actively enforced.

Limit	What it controls
Maximum upload size	The largest original size a single tenant-owned upload may be.
File compression	A capability that allows the configured compression mode; it is not a second size limit.

The former separate upload-size allowance without compression is retired and is not part of the active catalog.

Who it affects: anyone who uploads a file (for example, survey media or attachments).
When it applies: at the moment a file is uploaded.
What happens when reached: content validation rejects an oversized upload before it is stored. Existing files are unaffected.
Compression: when File compression is not included, compression is disabled even if the platform compression mode is otherwise optional or required.

The per-file limits here cap the size of one file.
Your total storage limit caps the sum of all your files. See Users and Storage Limits.

A file can be rejected either because it is individually too large, or because adding it would exceed your total storage quota.

Tenant-owned metered uploads require a resolved subscription and a positive effective Maximum upload size allowance. Missing, zero or negative values, including -1, refuse a new upload before storage reservation or file writes; retained files are unchanged.
The active catalog bounds the configurable value between 0 and 250 MiB. This is a finite per-file ceiling, not an unlimited sentinel. Valid current capacity add-ons contribute through the existing entitlement resolver.
Server-authored organization/mobile branding has a separate bounded, nonmetered exemption. It still validates content and size, encrypts files and preserves ownership.
Total storage is separate: a Storage allowance of 0 leaves no storage capacity, while -1 is treated as unlimited by the storage reservation path.

Support