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.

The upload-size limit and compression capability

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

The retired MaxFileUploadSizeBytesWithoutCompression key 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 CanCompressFiles is off, 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.

The current upload pipeline applies a per-file validator cap only when MaxFileUploadSizeBytes is positive and not -1.
Configure a positive value to enforce a cap. The active catalog currently bounds this value between 0 and 250 MiB; -1 is not offered by those bounds.
Total storage is separate: MaxStorageBytes = 0 leaves no storage capacity, while -1 is treated as unlimited by the storage reservation path.