Skip to main content

YAML Dummy Data Generator

Generate YAML dummy data as a list of flat records (Custom) or named collections (presets) for fixtures and imports.

Dataset

Output

This page focuses on YAML output. Use templates and fields below, then Generate and Download.

Quick Options (Rows):
Preset tables
Edited

    Field customizations apply for this session only and are not saved after reload.

    Configuration changed since the last generate. Regenerate before downloading the updated dataset.
    Field name Type Options

    The Columns control matches the field list: increasing it appends columns; decreasing it removes trailing columns (you’ll be asked to confirm if you edited fields).

    Also updates available contact fields
    Field separator
    Output size
    Max 25
    Max 10 · ZIP when > 1
    Max 10

    Quick use cases

    Create flat YAML fixtures for application tests. Test YAML parsing and data-import workflows. Export readable preset collections for documentation samples.

    Common generator issues

    A consumer expects nested configuration instead of flat records. Duplicate field names are blocked before generation. Field names do not match the target schema.

    Generator feature notes

    • Custom YAML is a list of flat maps.
    • Preset YAML uses table names as top-level keys.
    • Optional seed applies to presets; Custom ignores seed.

    Feature boundaries

    Custom mode: up to 5,000 records per file and 25 fields. Presets export named collections in one YAML document. Not intended for Kubernetes-style nested manifests.

    Related tools

    Sample output structure

    - id: 1
      name: John
      email: john@example.com

    Dataset generator FAQ

    What YAML structure does Custom mode produce?

    A YAML list where each item is a flat record containing the configured fields.

    Can it generate Kubernetes manifests?

    No. The generator creates flat record datasets (or named preset collections) and does not produce nested cluster schemas.

    How do presets differ from Custom YAML?

    Presets emit an object/map of table arrays instead of a single top-level list.