Format Set — Fruit Still Life (PNG)
A 1024×1024 fruit still life exported as PNG — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
A 1024×1024 fruit still life exported as PNG — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
A 1024×1024 fruit still life exported as JPG — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
A 1024×1024 fruit still life exported as WEBP — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
A 1024×1024 fruit still life exported as GIF — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
A 1024×1024 fruit still life exported as BMP — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
A 1024×1024 fruit still life exported as TIFF — one member of a conversion set that carries identical content across formats, so you can convert one and diff against the others.
A 1024×1024 fruit still life exported as AVIF — the modern-codec member of the conversion set.
A 1024×1024 fruit still life exported as HEIC — the HEIF/HEVC member of the conversion set, the format modern phones use for photos.
A 1024×1024 fruit still life exported as HEIF — the HEIF/HEVC member of the conversion set, the format modern phones use for photos.
A Windows ICO containing four square sizes (16/32/48/64 px) of a simple app glyph — the classic favicon/desktop-icon container. Handy for testing icon extraction and multi-size rendering.
A 12-frame animated PNG (APNG) of a rotating arc — a lossless, alpha-capable alternative to animated GIF. Useful for testing APNG support, frame extraction, and GIF↔APNG conversion.
A 256×256 fruit still-life image saved as uncompressed Truevision TGA — a format common in games and 3D texturing. For testing TGA decoders and conversion to modern formats.
A 256×256 fruit still-life image as binary Netpbm P6 (24-bit colour) — the minimal, header-plus-raw-pixels family used across Unix imaging tools. For testing Netpbm parsers and conversion.
A 256×256 fruit still-life image as binary Netpbm P5 (8-bit greyscale) — the minimal, header-plus-raw-pixels family used across Unix imaging tools. For testing Netpbm parsers and conversion.
A 256×256 fruit still-life image as binary Netpbm P4 (1-bit bitmap) — the minimal, header-plus-raw-pixels family used across Unix imaging tools. For testing Netpbm parsers and conversion.
The same 512px source saved at JPEG quality 10 — part of a q10/50/90 ladder for comparing compression artefacts at a glance.
The same 512px source saved at JPEG quality 50 — part of a q10/50/90 ladder for comparing compression artefacts at a glance.
The same 512px source saved at JPEG quality 90 — part of a q10/50/90 ladder for comparing compression artefacts at a glance.
A 16-bit (deep-colour) grayscale PNG holding a smooth 0–65535 gradient — for testing high-bit-depth support and spotting banding when a tool truncates to 8-bit.
The fruit still life converted to the CMYK (print) colour space and saved as a JPEG — for testing CMYK decoding and CMYK→RGB conversion. Some web viewers render CMYK JPEGs with a colour shift.
A generic sample brand logo as scalable vector graphics — a gradient mark plus a wordmark — for testing SVG rendering, rasterisation, and vector-to-raster conversion. Opens in the in-browser editor.
A single stroke-style UI icon (a document) as a 24×24 SVG — the kind of vector icon used in interfaces, for testing icon rendering, recolouring, and SVG-to-PNG conversion.
A bar chart drawn as vector SVG — axis, gridlines, labelled bars — the scalable counterpart to the raster chart images, for testing SVG chart rendering and vector conversion.
An animated loading spinner using SMIL (animateTransform) — a self-contained animated SVG for testing whether a renderer or converter handles SVG animation, and how it rasterises an animated frame.
A flat vector landscape — gradient sky, sun, layered hills, and trees built from bezier paths — a richer SVG for testing gradient and path rendering, thumbnailing, and vector conversion.
A pure 440 Hz sine tone stored as AIFF — Apple's big-endian 16-bit PCM container, 3 seconds, 44.1 kHz mono. A clean reference for testing AIFF decoders and WAV↔AIFF conversion.
A pure 440 Hz sine tone stored as a Sun/NeXT AU file — big-endian 16-bit PCM, 3 seconds, 44.1 kHz mono. A compact reference for AU decoding and format conversion.
A pure 1 kHz sine tone stored as AIFF — Apple's big-endian 16-bit PCM container, 3 seconds, 44.1 kHz mono. A clean reference for testing AIFF decoders and WAV↔AIFF conversion.
A pure 1 kHz sine tone stored as a Sun/NeXT AU file — big-endian 16-bit PCM, 3 seconds, 44.1 kHz mono. A compact reference for AU decoding and format conversion.
The lossless PCM WAV source for the audio conversion set — the same 3-second tone every other codec in this group is encoded from. Use it as the reference when diffing encoders.
The source clip as constant-bitrate MP3 (LAME, 192 kbps) — the most universally supported lossy audio format. For testing MP3 decoders, players, and conversion.
The same clip as variable-bitrate MP3 (LAME V2) — for testing VBR handling, seeking, and duration estimation against the CBR twin.
The clip as FLAC — free lossless audio compression. Byte-for-byte recoverable to the source PCM; for testing lossless decoders and conversion.
The clip as Ogg Vorbis — a royalty-free lossy codec. Browser-playable; for testing Vorbis decoding and Ogg conversion.
The clip as Opus — the modern low-latency codec used by WebRTC and streaming. Browser-playable; for testing Opus decoding and conversion.
The clip as raw AAC in an ADTS stream — the codec behind most streaming and mobile audio. For testing AAC decoders and remux into MP4.
The clip as AAC in an MP4/M4A container (faststart) — Apple's default audio container. For testing M4A parsing and MP4 audio conversion.
The clip as Apple Lossless (ALAC) in an M4A container — lossless, unlike the AAC M4A twin. For testing ALAC decoding and lossless conversion.
The clip as Windows Media Audio (WMA v2) in an ASF container — Microsoft's lossy codec. For testing WMA decoding and conversion to open formats.
The clip as AC-3 (Dolby Digital) — the multichannel codec used in DVD/broadcast. Rendered here in stereo; for testing AC-3 decoding and conversion.
The clip as an M4R iPhone ringtone — AAC in an MP4 container with the ringtone extension. For testing that a converter maps M4R↔M4A correctly.
The clip resampled to 8 kHz mono and encoded as AMR narrowband — the telephony/voice-note codec. For testing AMR decoding and speech-codec conversion.
A Word document with styled headings, bold/italic runs, a table, and an embedded image — for testing DOCX parsers and converters against a rich document.
A minimal Word document of plain paragraphs with no styling — the simplest valid DOCX for baseline parser testing.
A two-sheet workbook where a Summary sheet references a Data sheet with SUM and arithmetic formulas — for testing spreadsheet parsers, formula evaluation, and converters.
A Rich Text Format document exercising bold, italic, underline, colour, headings, and a bullet list — all as plain control words. For testing RTF parsers, text extraction, and RTF→DOCX/PDF conversion.
The simplest possible RTF: one monospace font and a couple of paragraphs, no styling. A minimal baseline for RTF parsers and conversion tools.
An OpenDocument Text file carrying the same content as the formatted DOCX — styled heading, bold/italic runs, and a table. The open twin in a DOCX↔ODT conversion set.
An OpenDocument Spreadsheet with the same tabular data as the plain XLSX and legacy XLS — a member of an XLSX↔ODS↔XLS conversion set for spreadsheet importers.
A legacy Excel 97–2003 (.xls / BIFF8) workbook holding the same tabular data as the plain XLSX and ODS — for testing legacy-format readers and XLS↔XLSX conversion.
A three-slide OpenDocument Presentation with titles and body text — for testing ODP readers and slide converters. Original content, free to use.
The formatted Word document saved as legacy binary .doc (Word 97-2003, OLE compound file) via LibreOffice. For testing legacy-Office parsers and DOC→DOCX conversion.
A pitch-deck slide set saved as legacy binary .ppt (PowerPoint 97-2003, OLE compound file) via LibreOffice. For testing legacy-Office parsers and PPT→PPTX conversion.
A SubRip (SRT) subtitle track with three timed cues — the most common subtitle format. Paired with the WebVTT twin for testing subtitle parsers and SRT↔VTT conversion.
A WebVTT subtitle track with three timed cues — the HTML5 <track> subtitle format. Paired with the SRT twin for testing subtitle parsers and VTT↔SRT conversion.
A workbook with a data table plus a native bar chart and a line chart bound to the cells — for testing whether spreadsheet parsers and XLSX-to-PDF converters preserve and render embedded charts.
A dashboard sheet exercising the features importers miss: a merged title cell, a three-colour conditional-formatting scale, a data-validation dropdown, cell borders, and frozen panes.
A four-slide presentation where every slide carries speaker notes in the notes pane — for testing notes extraction and whether converters preserve the notes alongside the slides.
A Word document with real tracked changes — insertions and deletions attributed to two reviewers with timestamps — for testing how tools read, accept, reject, or preserve revisions.
A Word document with two anchored reviewer comments — for testing comment extraction and whether converters preserve or drop review annotations.
A 500-row dataset of fake but realistic users (name, email, address, date of birth), generated with a fixed seed. Paired with a JSON twin.
The 500-row users dataset as a JSON array — the format twin of the CSV version, for testing import and conversion.
A 1000-row orders dataset whose user_id references the users dataset — a relational fixture for testing joins and import flows. Paired with a JSON twin.
The 1000-row orders dataset as JSON — the format twin of the CSV version, relational to the users dataset.
A small but complete OpenAPI 3.1 description (two paths, three schemas) in JSON — for testing API tooling, mock servers, client codegen, and docs generators.
The same OpenAPI 3.1 description in YAML — the format most API definitions ship in. Paired with the JSON twin for testing YAML↔JSON conversion and spec parsers.
A GraphQL Schema Definition Language (SDL) file with queries, a mutation, object/input types, and an enum — for testing GraphQL schema parsers, linters, and code generators.
A proto3 Protocol Buffers schema with messages, an enum, and a repeated field — for testing protobuf compilers (protoc), codegen, and schema tooling.
Page 1 of a paginated JSON API response (users), with page metadata and a `hasMore` flag. Paired with page 2 for testing pagination and infinite-scroll logic.
Page 2 (the final page) of a paginated JSON API response. Paired with page 1 for testing pagination, `hasMore` handling, and list merging.
A 404 error body in RFC 9457 (problem+json) form, with type, title, status, detail, and instance — for testing structured error handling and problem-detail parsers.
A 422 validation-error response with a machine-readable list of field errors — for testing form-validation surfacing and error mapping.
A sample environment (.env) file with typical configuration keys and placeholder values — for testing dotenv parsers and config loaders. Contains no real secrets.
A sample multi-stage Dockerfile with a build stage and a slim runtime stage — for testing Dockerfile parsers, linters (hadolint), and syntax highlighting. Illustrative only.
A sample docker-compose file defining a web service with Postgres and Redis dependencies — for testing Compose parsers and YAML tooling.
A W3C Web App Manifest (JSON) with name, theme colours, and icon set — for testing PWA install prompts and manifest validators.
A small employee table as Apache Parquet — the columnar format at the heart of modern data lakes and analytics. For testing Parquet readers (pandas, Spark, DuckDB) and conversion.
The same employee table as Apache ORC — the columnar format common in the Hive/Hadoop ecosystem. For testing ORC readers and Parquet↔ORC conversion.
The same table as Feather (Arrow IPC file) — the zero-copy on-disk form of an Apache Arrow table. For testing Arrow readers and fast columnar interchange.
The same records as Apache Avro — a compact row-based binary format that embeds its own schema, widely used in Kafka pipelines. For testing Avro decoders and schema evolution.
The records as MessagePack — a compact binary serialization that maps onto the JSON data model, common in caches and RPC. For testing MessagePack codecs and JSON↔MessagePack conversion.
The records as CBOR — the IETF concise binary object representation used in IoT and COSE/WebAuthn. For testing CBOR decoders and JSON↔CBOR conversion.
The records as BSON — the binary-JSON encoding MongoDB stores documents in. For testing BSON decoders and JSON↔BSON conversion.
A small HDF5 file with a compound 'employees' dataset and a numeric 'readings' grid — the hierarchical format used across science and ML. For testing h5py/HDF5 readers and conversion.
The employee table as a dBase (DBF) file — the venerable xBase table format still emitted by GIS tools and legacy databases. For testing DBF readers and DBF→CSV conversion.
A single protobuf User message in binary wire format (varint + length-delimited fields) — the serialized counterpart to the user.proto schema. For testing protobuf decoders without the generated code.
A realistic e-commerce product catalogue (200 rows) — part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.
The e-commerce products table as a JSON array — the format twin of the CSV, for import and conversion testing.
The e-commerce products table as Apache Parquet — the columnar twin, for testing analytics engines (pandas, DuckDB, Spark).
A realistic e-commerce customer directory (500 rows) — part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.
The e-commerce customers table as a JSON array — the format twin of the CSV, for import and conversion testing.
A realistic e-commerce order lines (customer_id → customers, product_id → products) (2000 rows) — part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.
The e-commerce orders table as a JSON array — the format twin of the CSV, for import and conversion testing.
The e-commerce orders table as Apache Parquet — the columnar twin, for testing analytics engines (pandas, DuckDB, Spark).
A relational SQL schema (products, customers, orders with primary and foreign keys) plus sample INSERTs — the DDL twin of the e-commerce dataset, for testing schema import and migrations.
A year of daily OHLCV stock candles (open/high/low/close/volume) as a seeded random walk — a realistic finance time-series for testing charting, indicators, and importers. JSON twin included.
A day of IoT sensor readings (temperature, humidity, pressure) at one-minute intervals from three sensors, with a realistic daily cycle plus noise — for testing time-series ingestion and downsampling. JSON twin included.
A sample HL7 FHIR R4 bundle with a Patient plus vital-sign Observations, an Encounter, and a Condition — a realistic healthcare-interoperability fixture for testing FHIR parsers and mappers. Synthetic data, not a real person.
A 50,000-row transactions dataset — an in-repo 'large' fixture for testing streaming CSV parsers, import performance, and pagination. Deterministic (fixed seed).
A valid Jupyter notebook (nbformat 4.5) with markdown cells, code cells, and real outputs (stdout stream and an execute result) — for testing notebook parsers, nbconvert, and JSON tooling.
A Mermaid flowchart of an order-fulfilment process as diagrams-as-code — for testing Mermaid rendering, diagram-to-image conversion, and Markdown pipelines that embed Mermaid.
A Graphviz DOT directed graph describing a fulfilment pipeline — for testing DOT parsing, Graphviz rendering, and DOT-to-SVG/PNG conversion.
A PlantUML sequence diagram of an order interaction (customer, store, warehouse) as diagrams-as-code — for testing PlantUML parsing and diagram rendering pipelines.
A draw.io (diagrams.net) diagram in its native mxGraphModel XML — a small flowchart — for testing draw.io import/export and XML parsing of diagram files.
A sample JSON Web Token (JWT) signed with HS256 using a published example secret — verifiable but powerless — for testing JWT decoders and validators. Sample only, never for production. Paired with its decoded claims.
A clean invoice template as a Word document with a line-item table and total. Paired with a PDF twin of the same layout.
The invoice template as a print-ready PDF — the format twin of the DOCX version, for converter testing and direct printing.
A realistic sales quotation with a five-line item table, subtotal, tax, and validity terms — as an editable Word document, twinned with a print-ready PDF.
The sales quotation as a branded, print-ready PDF with a line-item table and totals — the format twin of the DOCX quote, for converter testing and direct sending.
A purchase order with buyer and vendor blocks, a line-item table, totals, and Net-30 terms — an editable Word document paired with a PDF twin.
The purchase order as a branded print-ready PDF with a line-item table and totals — the format twin of the DOCX version for converter and print testing.
A company newsletter as an editable Word document with a masthead and three short articles — twinned with an HTML email version of the same content.
A ZIP archive — 3 files at the root, no directories. Deterministic (fixed member timestamps) and safe to extract anywhere.
A ZIP archive — files organised into data/ and docs/ subfolders. Deterministic (fixed member timestamps) and safe to extract anywhere.
A ZIP archive — a file nested six directory levels deep. Deterministic (fixed member timestamps) and safe to extract anywhere.
A ZIP archive — UTF-8 filenames: accents, Japanese, emoji. Deterministic (fixed member timestamps) and safe to extract anywhere.
A ZIP archive — 100 tiny files for throughput testing. Deterministic (fixed member timestamps) and safe to extract anywhere.
A valid ZIP with zero entries — the empty-archive edge case for testing how unarchivers handle a container with nothing inside.
A Java Archive (JAR) — a ZIP with a META-INF/MANIFEST.MF and resource files only (no .class bytecode). For testing JAR/ZIP readers and manifest parsing.
A uncompressed USTAR of a small source tree — for testing tar extraction and the TAR container. Member timestamps are fixed for reproducibility.
A gzip-compressed tar of a small source tree — for testing tar extraction and the TGZ container. Member timestamps are fixed for reproducibility.
A bzip2-compressed tar of a small source tree — for testing tar extraction and the TBZ2 container. Member timestamps are fixed for reproducibility.
A xz/LZMA-compressed tar of a small source tree — for testing tar extraction and the TXZ container. Member timestamps are fixed for reproducibility.
A single text file compressed with gzip — the container-free codec on its own, for testing decompression and codec detection.
A single text file compressed with bzip2 — the container-free codec on its own, for testing decompression and codec detection.
A single text file compressed with xz/LZMA — the container-free codec on its own, for testing decompression and codec detection.
A 7-Zip archive using LZMA2 compression, containing a small documented file tree. For testing 7z extraction and conversion.
A password-protected 7z archive (AES-256, encrypted header). The password is “novus-example” — printed here on purpose so you can test encrypted-archive extraction. Contains only harmless sample text.
A real ISO 9660 disk image with Joliet and Rock Ridge extensions for long filenames, holding a few documented text files. For testing ISO mounting, extraction, and conversion.
A text file compressed with Zstandard (.zst) — the container-free codec on its own — for testing zstd decompression and codec detection.
A text file compressed with the LZ4 frame format (.lz4) — the container-free codec on its own — for testing LZ4 decompression and codec detection.
A minimal WARC 1.0 web archive with a warcinfo record and an HTTP response record capturing a small HTML page — for testing WARC parsers and web-archive tooling.
A valid EPUB 3 e-book with a cover image, an EPUB navigation document, styled chapters, and a correctly stored OCF mimetype. Original content, for testing EPUB readers and EPUB→other conversion.
An intentionally invalid EPUB: identical to the valid twin except its OCF mimetype entry is compressed and mislabelled as application/zip — a real EPUB spec violation. For testing how readers and validators handle a malformed container. Clearly labelled; harmless content.
A FictionBook (FB2) e-book — a single self-contained XML file with full title and document metadata and three chapters. Popular in e-reader ecosystems; for testing FB2 parsers and FB2→EPUB conversion.
A CBZ comic archive — a ZIP of sequentially named JPEG pages, the standard container for digital comics. Built from generated pages; for testing comic readers and CBZ→PDF conversion.
The valid EPUB converted to MOBI (Mobipocket) with Calibre — the classic Kindle format. For testing MOBI readers and EPUB→MOBI conversion.
The valid EPUB converted to AZW3 (Kindle KF8) with Calibre — the modern Kindle format. For testing AZW3 readers and EPUB→AZW3 conversion.
A 10 mm cube as ASCII STL — human-readable facet/normal/vertex records. The most portable 3D-print mesh format; for testing STL parsers and slicers.
The same 10 mm cube as binary STL — an 80-byte header, a triangle count, and packed little-endian floats. Compact; for testing binary-STL readers.
A 10 mm cube as a Wavefront OBJ — plain-text vertices and triangular faces, the lingua franca of 3D asset exchange. For testing OBJ importers and conversion.
A 10 mm cube as 3MF — the modern OPC-packaged manufacturing format (a ZIP of model XML plus relationships). For testing 3MF readers and slicers.
A 10 mm cube as binary glTF (GLB) — the dominant modern format for 3D on the web and in AR, with per-face normals packed into one self-contained file. Powers the interactive 3D preview on this site; for testing glTF loaders and conversion.
A 10 mm cube drawn as 12 DXF LINE entities — the AutoCAD interchange format, written with ezdxf. For testing DXF parsers and CAD conversion.
An isometric cube as Encapsulated PostScript — a 2D vector illustration with three shaded faces. For testing EPS/PostScript rendering and vector conversion.
A minimal, well-formed STEP AP214 file holding the eight corner points of a 10 mm cube. For testing STEP header and entity parsing and CAD-exchange tooling.
A minimal, well-formed IGES 5.3 file with a single LINE entity and correct Start/Global/Directory/Parameter/Terminate sections. For testing IGES parsers and CAD conversion.
A 10 mm cube as text glTF 2.0 — the JSON scene with its binary buffer embedded as a data URI, the human-readable sibling of the GLB. For testing glTF parsers and GLB↔glTF conversion.
A 10 mm cube as ASCII PLY (Stanford polygon format) — plain-text vertex and face lists common in 3D scanning and research. For testing PLY parsers and conversion.
The same cube as binary little-endian PLY — the compact form of the Stanford polygon format. For testing binary-PLY readers.
A 10 mm cube as OFF (Object File Format) — the minimal vertex/face text format from Geomview, common in computational geometry. For testing OFF parsers and conversion.
A 10 mm cube as COLLADA (.dae) — the XML digital-asset-exchange format used across 3D tools and game engines. For testing COLLADA parsers and conversion.
A 10 mm cube as VRML97 (.wrl) — the classic Virtual Reality Modeling Language scene format, ancestor of X3D. For testing VRML parsers and conversion.
A 10 mm cube as X3D — the XML successor to VRML for web and interchange 3D. For testing X3D parsers and VRML↔X3D conversion.
A 10 mm cube as USDZ — Pixar's Universal Scene Description packaged as a stored zip, the format Apple uses for AR Quick Look. For testing USD/USDZ readers and conversion.
The Novus Sans Sample demonstration typeface as TrueType (glyf outlines) — one member of a TTF/OTF/WOFF/WOFF2 conversion set built from scratch with fontTools. Original and free to use; a fixture for testing font loading, subsetting, and conversion.
The Novus Sans Sample demonstration typeface as WOFF (TrueType-flavoured web font) — one member of a TTF/OTF/WOFF/WOFF2 conversion set built from scratch with fontTools. Original and free to use; a fixture for testing font loading, subsetting, and conversion.
The Novus Sans Sample demonstration typeface as WOFF2 (Brotli-compressed web font) — one member of a TTF/OTF/WOFF/WOFF2 conversion set built from scratch with fontTools. Original and free to use; a fixture for testing font loading, subsetting, and conversion.
The Novus Sans Sample demonstration typeface as OpenType/CFF outlines — one member of a TTF/OTF/WOFF/WOFF2 conversion set built from scratch with fontTools. Original and free to use; a fixture for testing font loading, subsetting, and conversion.
A short H.264 test clip in an MP4 container (yuv420p, faststart) — the most widely supported web and mobile video format. Video-only and tiny; for testing players, thumbnailers, and MP4→other conversion.
The same clip as WebM/VP9 — the royalty-free web video format. Video-only; for testing HTML5 <video>, VP9 decoding, and WebM conversion.
The clip in a Matroska (MKV) container with H.264 video — the flexible open container used for rich multi-track media. For testing MKV demuxing and remux/conversion.
The clip in a QuickTime (MOV) container with H.264 video — Apple's container, common from cameras and editors. For testing MOV parsing and MOV→MP4 conversion.
The clip as Motion-JPEG in a classic AVI (RIFF) container — every frame an independent JPEG. For testing legacy AVI readers, MJPEG decoding, and AVI→modern-codec conversion.
The clip as Ogg Theora — a fully open, royalty-free format. Browser-playable; for testing Theora decoding and Ogg video conversion.
The clip as MPEG-1 in an MPEG program stream (.mpg) — the VCD-era format. For testing legacy MPEG demuxing and conversion to modern codecs.
The clip as M4V — Apple's MP4 variant used by iTunes. Browser-playable; for testing M4V handling and M4V↔MP4 conversion.
The clip as 3GP — the 3GPP mobile container from the feature-phone era. For testing 3GP demuxing and conversion.
The clip as an MPEG transport stream (.ts) — the container behind HLS streaming and broadcast. For testing TS demuxing and HLS tooling.
The clip as Flash Video (.flv) with H.264 — the legacy web-streaming container. For testing FLV demuxing and conversion to MP4.
The clip as Windows Media Video (WMV2 in an ASF container) — Microsoft's legacy video format. For testing WMV decoding and conversion to open formats.
The clip as DivX-style MPEG-4 ASP in an AVI container — the codec that defined early desktop video. For testing MPEG-4 Part 2 decoding and AVI conversion.
A ZIP bundling the MP4 and WebM test clips with a README — a 'video archive' for testing pipelines that unpack an archive and then transcode its contents. Stored (not re-compressed), since the clips are already compressed.
A standards-compliant plain-text email message (.eml) with full headers — the simplest valid RFC 822 message for testing email header parsing and EML import.
A multipart/alternative email carrying both a plain-text and an HTML body — for testing MIME part selection, HTML-part handling and sanitising, and multipart parsing.
A multipart/mixed email with a base64-encoded CSV file attachment — for testing attachment detection, decoding, and extraction from an EML message.
An mbox mailbox concatenating a short three-message email thread with the classic 'From ' separator lines and >From body escaping — for testing mailbox splitting and thread reconstruction.
We use Google Analytics. It sets no analytics cookies until you allow the Analytics category below. See our cookie policy.