Bulk mock SQL INSERTs
Define a table and columns, then generate bulk INSERT statements with fake data. Choose Standard, MySQL, or PostgreSQL dialect. Runs locally.
Click Generate
How to seed test data
Define your columns and dialect, click Generate, paste the SQL into psql, mysql, or your migration runner.
- 01
Name table
Used as the INSERT target (identifier-quoted per dialect).
Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.
tableinpututf-8client-sidevalidatedtable · textusers · setusers
loaded · parsedclient-side - 02
Define columns
Pick name + type. Eight built-in fake types.
Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.
schemaoptionslivememoisedtogglescols · memoised4 · liveid uuid · full_name
options set · memoisedlive - 03
Pick dialect
MySQL uses backticks, PostgreSQL TRUE/FALSE plus double-quotes.
Randomness — where used — comes from
crypto.getRandomValues, neverMath.random. Heavy work sits inuseMemo.dialectcomputeinstantlocaldeterministicout · instantsql · computedINSERT INTO …;
computed · instantinstant - 04
Generate & save
Copy or download .sql for migrations and CI fixtures.
Copy writes through
navigator.clipboardand downloads use aBlob— zero network traffic. Same input plus same options always yield the same bytes.exportcopydownloadzero-networkreproducibleok · copiedready · copiedSaved
shipped · ready to shipsuccess
Pro tips for everyday utilities
Reach for crypto.getRandomValues
Cryptographically random for IDs, tokens, salts. Math.random is for animation and games, not security.
Mock data with seeds
Faker-style libraries can be seeded so tests are reproducible. Embed the seed in the fixture file.
Reference cards beat memory
Cheatsheets for Vim, Git, Docker, Linux signals are faster than man pages when you’re mid-flow.
Browser APIs vary
Touch events, gamepads, and clipboard differ across vendors. Feature-detect before use.
Persist in the right place
localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data.
When to mock SQL inserts
Seed data, demos, CI fixtures.
Local seed scripts
Bootstrap a dev database in seconds. Random values come from crypto.getRandomValues — cryptographically secure for tokens, salts, and session IDs. Math.random is deterministic enough for animations but predictable enough to be a security bug.
CSPRNG-backedMigration smoke tests
Verify schemas with realistic rows. Pair with hashids, ULID, or UUID v7 when you need both random and sortable — useful for primary keys, public-facing IDs, and event log ordering without a sequence column.
reproducibleDemo databases
Populate dashboards for screenshots. Output is deterministic given the same seed, so fixtures and tests stay reproducible across CI runs and contributor machines. Embed the seed in the fixture file for full replay.
snappyLoad testing
Generate 2k rows for perf benchmarks. Heavy work runs through useMemo so the UI stays snappy on large inputs. Same input + same options yields identical bytes — the kind of stability snapshot tests rely on.
feature-detectedOnboarding
Give new engineers a populated DB on day one. Storage tools persist to the right backend: localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data. Pick the right shelf and quota worries disappear.
deterministicCross-dialect
Test schemas in MySQL + Postgres simultaneously. Browser feature detection: clipboard, fullscreen, gamepad, and Web Bluetooth APIs gracefully fall back when unavailable. No surprise white screens on Safari or older Firefox.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.