Are these real, parseable files?

Yes. Unlike most other categories on this site, these files are not padded placeholders — the JSON, XML, YAML, SQL, HTML, CSS, JS, and Markdown are all valid and will parse or render correctly.

Can I use these to test that my parser rejects bad input?

Not directly — these files are intentionally valid. Use them as a baseline for the happy path, then modify a copy to create invalid test cases.

Do the JSON, XML, and SQL files describe the same data?

Yes. They all represent the same small sample product dataset, so you can compare how the same data looks across formats.

Can I use these in an automated test suite?

Yes. Each file has a stable, direct URL, so you can fetch it in a CI pipeline instead of committing fixtures to your repository.

Which formats are available?

JSON, XML, YAML, SQL, HTML, CSS, JS, Markdown, and LOG.

Code & Data

Real, valid sample data and code files: JSON, XML, YAML, SQL, HTML, CSS, JS, Markdown, and a plain-text log — all describing the same small sample dataset.

What these files actually are

Every file below is real and valid for its format - the JSON parses, the XML validates, the SQL runs, the HTML/CSS/JS render in a browser, and the Markdown renders as expected. Unlike the other categories on this site, these aren't padded to a target size, since what matters for code and data files is correct, parseable structure — not a specific byte count.

sample-config.yaml

YAML · 381 B

Download
sample-data.json

JSON · 625 B

Download
sample-data.xml

XML · 560 B

Download
sample-dump.sql

SQL · 802 B

Download
sample-page.html

HTML · 397 B

Download
sample-readme.md

MD · 620 B

Download
sample-script.js

JS · 634 B

Download
sample-style.css

CSS · 212 B

Download
sample.log

LOG · 657 B

Download

Common use cases

Parser and importer testing

Feed a real JSON, XML, YAML, or SQL sample into a parser, ETL job, or database import script to confirm it handles valid, structured input correctly.

Linter and formatter checks

Run a linter, formatter, or static-site generator against a real HTML, CSS, JS, or Markdown file instead of writing throwaway fixtures by hand.

Log-viewer and monitoring smoke tests

Load a realistic multi-line log file into a log viewer, aggregator, or alerting rule to confirm timestamps and levels are parsed correctly.

CI pipeline fixtures

Reference a stable, direct URL from a test suite or CI job instead of committing small data fixtures to your repository.

Formats & variants

JSON: The standard data-interchange format for web APIs and config files.
XML: A tag-based markup format still common in enterprise data interchange and config.
YAML: A human-readable format widely used for application and CI configuration.
SQL: A plain-text database dump with table creation and insert statements.
HTML / CSS / JS: A minimal real webpage with a linked stylesheet and script.
Markdown: A README-style file with headings, a list, a code block, and a table.
LOG: A plain-text application log with timestamps and mixed severity levels.

Frequently asked questions

Are these real, parseable files?: Yes. Unlike most other categories on this site, these files are not padded placeholders — the JSON, XML, YAML, SQL, HTML, CSS, JS, and Markdown are all valid and will parse or render correctly.
Can I use these to test that my parser rejects bad input?: Not directly — these files are intentionally valid. Use them as a baseline for the happy path, then modify a copy to create invalid test cases.
Do the JSON, XML, and SQL files describe the same data?: Yes. They all represent the same small sample product dataset, so you can compare how the same data looks across formats.
Can I use these in an automated test suite?: Yes. Each file has a stable, direct URL, so you can fetch it in a CI pipeline instead of committing fixtures to your repository.
Which formats are available?: JSON, XML, YAML, SQL, HTML, CSS, JS, Markdown, and LOG.