loremfile

FAQ

Yes, that is what the site is for. CORS is open to every origin, files carry Cross-Origin-Resource-Policy: cross-origin, and byte ranges work, so an <img>, <video> or fetch() on any page can use them directly.

Is there a rate limit?

Keep automated traffic under 30 requests per second per IP. Faster clients may be rate-limited. A CI job that needs many files should download them once and cache them.

Why is there no ?download parameter?

Query strings do not change a response, so every request for a path is answered by the same cached object. Save a file with curl -O, wget or your browser's save command.

Why do search engines not index the files?

Files are served with X-Robots-Tag: noindex, so search results lead to the format pages, which explain what each file is and give you its URL.

Can I mirror the files?

Yes. Every file is CC0 1.0, so you may copy it for any purpose without asking. Verify your copy against sha256sums.txt, and please download once rather than repeatedly.

Will a file ever change?

The bytes at a published path do not change. A defective file is replaced by a new path, and the old entry points to it. In rare cases a file can be withdrawn; see the terms of use.

Where do the files come from?

Every file is generated by the open-source tooling in the repository, inside a pinned container, from synthetic data. No file contains third-party media or real personal data, except that some images and PDFs rasterise glyphs from open-licensed fonts, which THIRD_PARTY.md in the repository lists.

Accessibility

The site targets WCAG 2.1 AA; report issues on GitHub.