Sample WOFF Files — Download Free Web Fonts for Testing
Web Open Font Format · .woff · MIME type font/woff
Download a sample WOFF file to test @font-face loading, CDN delivery, CORS on font requests, or a font-conversion pipeline. WOFF is a TrueType font wrapped in a zlib-compressed container with metadata, which is why these files are roughly 40 percent smaller than the matching TTFs while carrying identical outlines.
Every file is served with the correct font/woff MIME type and an open CORS header, so you can load them cross-origin from a test page without setting anything up. That makes them useful for reproducing the CORS font failures that are otherwise awkward to stage.
Download sample WOFF files
| File | Details | Size | Download |
|---|---|---|---|
sample-font-roboto-mono-regular.woff | Roboto Mono Regular · SIL Open Font License 1.1 | 54 KB | |
sample-font-lora-regular.woff | Lora Regular · SIL Open Font License 1.1 | 66 KB | |
sample-font-open-sans-regular.woff | Open Sans Regular · SIL Open Font License 1.1 | 78 KB | |
sample-font-roboto-regular.woff | Roboto Regular · SIL Open Font License 1.1 | 92 KB | |
sample-font-roboto-bold.woff | Roboto Bold · SIL Open Font License 1.1 | 94 KB | |
sample-font-inter-regular.woff | Inter Regular · SIL Open Font License 1.1 | 160 KB |
Use these files from the command line or CI
Every URL is stable and CORS-open. Pin the SHA-256 in your test and you will know the moment a fixture changes.
# Download one file curl -O https://pnb-website-bucket.s3.us-east-2.amazonaws.com/samples/fonts/woff/sample-font-roboto-mono-regular.woff # Verify it (SHA-256 is listed for every file above) shasum -a 256 sample-font-roboto-mono-regular.woff # Machine-readable index of every sample file curl https://pnb-website-bucket.s3.us-east-2.amazonaws.com/samples/index.json | jq '.files[] | select(.format=="woff")'
WOFF format at a glance
| Full name | Web Open Font Format |
|---|---|
| Extensions | .woff |
| MIME type | font/woff |
| Standard | WOFF 1.0 (W3C Recommendation, 2012) |
| Compression | zlib (per-table) |
| Magic bytes | 77 4F 46 46 ("wOFF") |
| MIME type | font/woff |
| Licence | SIL Open Font License 1.1 |
What people test with sample WOFF files
- @font-face loading and fallback behaviour
- Cross-origin font requests and CORS headers
- CDN caching and compression testing
- Font loading API and FOUT/FOIT behaviour
- Legacy browser fallback chains
Frequently asked questions
Should I still serve WOFF alongside WOFF2?
Only if you support browsers older than Chrome 36, Firefox 39, Safari 10 or Edge 14, which is under one percent of traffic in most markets. Modern practice is WOFF2 alone. Keep a WOFF fallback if your analytics show real users on old Android or Internet Explorer.
Why does my font fail to load with no error?
Nine times out of ten it is CORS. Fonts are fetched in CORS mode regardless of origin, so a cross-domain font needs Access-Control-Allow-Origin on the response. The browser reports a 200 in the network tab and silently declines to use the font. These files are served with an open CORS header so you can isolate that variable.
Can I use these fonts in a commercial project?
Yes. Every face is released under the SIL Open Font License 1.1, which permits use, modification, embedding and redistribution, commercially included. You may not sell the fonts on their own, and a modified version must not keep the original reserved font name. The full licence text is published alongside the files.
Are these variable fonts?
No. The upstream sources are variable, and we instance each to a single static weight before conversion, then delete the leftover fvar, avar, STAT and gvar tables. Static faces are what font loaders, subsetters and validators are normally tested against, and an orphaned variation table is a common source of confusing failures.
Do the files contain the full character set?
Yes, the full upstream character set — between 778 and 2,849 mapped codepoints depending on the family, covering Latin, Latin Extended, Greek and Cyrillic. Nothing is subset, so these are also useful for testing that your own subsetting pipeline actually reduces the file.
Are these WOFF files safe to download?
Yes. Every file is generated by our own open script from scratch — nothing is scraped or user-uploaded — and contains no scripts, macros or executables. The SHA-256 of each file is published on this page so you can verify what you received.
Can I use the sample WOFF files commercially?
Yes. They are free for any purpose, including commercial products, test suites, demos and redistribution, with no attribution required. There is nothing to license and no one to ask.
Can I hotlink these files or use them in CI?
Yes. Every link is a stable direct URL over HTTPS with Access-Control-Allow-Origin: * and long cache headers, so curl, wget, fetch() and test runners can pull them directly. A JSON index of every file is linked from each page (see the command-line section).
Related sample files
Free tools that work with WOFF
- Favicon Generator — Turn any logo into a complete favicon package — favicon.ico, all PNG sizes, Apple touch icon, and webmanifest — in one click.
- Test File Generator — Generate a dummy file of any exact size in your browser — 1 KB to 2 GB, random bytes, text, CSV or JSON.
Found a problem, or something that could be better? We read every message and we fix things quickly.
Testing a file pipeline? We build them.
Uploads, conversions, previews, document processing and media workflows are the kind of production systems Pine & Birch designs and runs for clients — which is why we needed these files in the first place.
See how we can help