Sample datasets

a few realistic test files for the tools on this site · updated 4 May 2026

Every tool here works just as well with your own data, but sometimes you just want something to drop in and see what the output looks like. The files below are small, realistic, and cover the obvious edge cases — including a couple of intentionally broken files for testing the validators. Each link saves the file to your machine; nothing is uploaded anywhere when you then drop it into a tool.

Small starter files

pyproject.toml

Standard Python project configuration file using Hatchling backend, defining metadata, dependencies, and settings for modern tools like Ruff and Pytest.

0.9 KB · 6 tables × 24 entries · download ↓

cargo.toml

Rust package manifest specifying crate metadata, feature flags, workspace members, and conditional dependencies for high-performance systems programming applications.

0.8 KB · 7 tables × 22 entries · download ↓

config-mixed.toml

A comprehensive DevOps configuration demonstrating complex TOML features including dotted keys, multi-line strings, date-time formats, and various numeric representations.

1.2 KB · 8 tables × 3 array items · download ↓

Larger datasets

Larger TOML files for stressing the formatter and the JSON/YAML round-trip — including an intentionally broken file to verify the validator's error positions.

monorepo-cargo.toml

A workspace-style Cargo.toml with eighty crate members and forty workspace dependencies — exercises array-of-tables and big inline tables.

2.4 KB · [workspace] · 80 members · download ↓

complex-pyproject.toml

A pyproject.toml with sixty production deps and four optional-dependency groups — covers nested keys and tool-specific sub-tables.

1.7 KB · [project] + tool sections · download ↓

broken-mixed-300.toml

Three hundred entries with ~20% intentionally invalid: missing values, unquoted strings, mixed quote styles, duplicate keys.

4.8 KB · 300 entries · ~60 broken · download ↓

How to use these

Click any card to download the file, then drop it on the input pane of whichever tool fits. The intentionally-broken files (with names like broken-*) are useful for trying the validators — they should report specific line numbers and reasons.

Want one added?

If you have a real-world file you'd love to see as a sample (anonymised, of course), email [email protected] and I'll add it. The smaller and weirder the better — the goal is to have files that exercise the tools, not pretty demos.

— S., [email protected]