About TrueFileSize
TrueFileSize provides downloadable fixtures for upload limits, parsers, storage pipelines, and QA workflows. Labels such as sample-10mb.pdf describe the intended test tier; the file card publishes the exact byte count to use when a boundary test must be precise.
The catalog currently contains 413 records across 52 formats. Each record uses the same verification evidence in its page, public API, and structured data so consumers can compare the filename, exact size, checksum, and integrity status.
52
File formats
413
Catalog records
1GB
Largest catalog file
0
Signup forms
What we stand for
Measured evidence
Each catalog record publishes the exact measured byte count, SHA-256 checksum, verification date, and a header-signature result when the format has a stable signature.
Integrity made explicit
Normal samples, intentionally invalid fixtures, and zero-byte fixtures are labeled separately. A header match is treated as a format hint, not proof of complete validity or safety.
Direct, stable downloads
Catalog files use stable CDN URLs and do not require an account or email form. Consumers should still cache fixtures and design automated tests for ordinary network failures.
Clear reuse terms
Downloadable sample files are provided under CC0 / Public Domain unless a specific page states otherwise. The license page defines the scope and practical limitations.
How we generate every file
Format-aware generators and encoders create the release artifacts. A streaming verifier then measures each artifact, calculates its SHA-256 checksum, and inspects a known header signature when one is available. Files intended for negative tests are kept only when their invalid or empty status is stated explicitly.
The catalog uses stable CDN paths. The checksum on each file page identifies the corresponding local release artifact and makes an unexpected byte change detectable.
For the full process, read how we generate files. Our editorial policy explains how we review file claims and guides, and the license page covers reuse rights. Use the contact page to report incorrect metadata, broken downloads, or guide corrections.
Editorial ownership
The publishing entity responsible for maintaining guides, catalog metadata, and the evidence policy.
Use TrueFileSize in your tests
- Browse sample files by size for the exact size you need.
- Hit the public files API to fetch the catalog in JSON.
- Read the blog for upload, storage, and QA tutorials.