randarium
Test Data

Fake File Generator

Create synthetic filenames, file paths, directory trees, MIME types, and document metadata for testing file handling, validation, and upload scenarios.

Also known as: file name · file path · directory

seeded · synthetic data

Presets

Output

No output yet — set your options and hit .
About this tool, tips & examples

What it does

The Fake File Generator produces synthetic file-system data: realistic filenames with proper extensions, full file paths, directory trees, MIME types, and document metadata. Generate up to 1,000 entries per run, seeded so a fixture set can be regenerated exactly.

Common use cases

  • Upload testing — filename lists covering common and awkward extensions for validating file-type checks.
  • File-manager UIs — plausible paths and trees to populate browsers, pickers, and breadcrumb components.
  • MIME handling — content-type fixtures for testing upload filters, preview logic, and storage routing.
  • Parser and validation tests — filenames with spaces, dots, and mixed case that shake out naive path handling.

Settings

  • Type — filenames, file paths, directory trees, MIME types, or document metadata (presets cover the first three).
  • How many — 1 to 1,000 entries per run, exportable as text, CSV, or JSON.
  • Seed — the same seed and settings always regenerate the identical set.

Privacy note

Everything is generated locally in your browser and never uploaded. The files don’t exist — these are synthetic names and metadata for testing file handling, with no actual file content behind them.

FAQ

Do the files actually exist? No — you get names, paths, and metadata, not file contents. That’s the point: you can test handling logic without creating or moving real files.

Can I test weird filenames? The generated names include realistic variety; for hostile cases (Unicode, extreme lengths, injection-shaped names) pair this with the Edge Case Strings generator.

Are MIME types matched to extensions? Types are drawn from real MIME conventions, making them right for testing content-type logic — including the mismatch cases your validator should catch.