Asset methodology

Small, representative fixtures

The published catalog favors common development scenarios over format volume: standard, silent, and low-resolution videos across WebM, MP4, and MOV, plus compact PDF and Office files. Images, PCM WAV audio, and structured text are generated locally when a permanent URL is unnecessary.

Metadata generation

Published-asset metadata is generated from source bytes using format-aware tools. The committed record includes exact byte size, SHA-256, verification date, MIME, and relevant properties such as dimensions, duration, codecs, frame rate, page count, sheet count, or slide count. Locally generated files are inspected in the browser.

Verification pipeline

Every published candidate passes a metadata check before the Astro build. The check reads the actual object bytes and compares the filename, path, MIME type, byte length, SHA-256, and format-specific fields with the committed manifest. A mismatch fails the release rather than updating public metadata implicitly.

Video candidates are probed for container, video and audio codecs, dimensions, duration, frame rate, and track presence. They are also opened by the browser test suite and served through a Range request that must return HTTP 206. PDF and Office candidates are checked for their file signatures, internal container structure, documented page, worksheet, or slide count, and successful download.

Hashes and reproducibility

SHA-256 is published as an integrity identifier, not as a security endorsement of arbitrary uploaded content. Consumers can compare the documented hash after download and pin it in a test suite. Browser-generated fixtures do not have permanent URLs, but deterministic presets such as PCM audio use stable inputs so repeated runs can be compared locally.

Stable URL policy

The 13 published assets are immutable. A content change requires a new filename and asset id; an existing public URL is not overwritten in place. Browser-generated outputs do not receive SEO detail URLs and may be downloaded directly from the current session.

Delivery boundaries

Astro pages, fonts, icons, posters, and social images are published by Cloudflare Pages. Test media is excluded from the Pages artifact and delivered from the dedicated R2 custom domain.

The download endpoint preserves the published filename and content type. Video delivery supports byte ranges for seeking and partial-content tests. Browser and CI checks verify a full download as well as an initial range before a release is accepted.

Compatibility and release control

Published files are tested in current Chrome, Safari, and Firefox where the format is supported. A release records the verification date and keeps the prior public bytes immutable. If content or encoding must change, TestFiles.dev creates a new asset id and filename, updates references deliberately, and leaves retired detail URLs non-indexable rather than disguising a replacement as the original file.