Pikkola Seed Studio, tool No. 42

Rows that come back exactly the same.

Describe the columns, choose what each one holds, and set a row count. One number, the seed, fixes the whole table: run it again next month on another machine and you get the same bytes. Then take it as JSON, CSV, SQL or TypeScript.

21
field types
5
presets
0
requests sent

The table

Describe the columns, get the rows

Every change below rewrites the table on the right. A column can be renamed, retyped, moved or given a share of nulls, and the preview follows as you type.

Start from

Columns

NULL is the share of cells left empty in that column. It is written as null in JSON, an empty cell in CSV, NULL in SQL and null in TypeScript.

The columns

Twenty one kinds of value

Each card shows a value from your current seed, so the samples move when the seed does and stay put when it does not.

uuid

A version 4 identifier, with the version and variant bits set the way the format requires.

id

A count, starting at the number you set, so a table has a key a join can use.

name

A first name and a last name from a short list written for this page.

email

A mailbox at example.com, example.org or example.net, and never at a real provider.

phone

The 555-01xx band, the UK 020 7946 0xxx band or 010-0000-, all set aside for fiction.

company

Two invented words, so no real business appears in a demo.

jobTitle

A role name such as Product Manager or QA Engineer.

country

A country name, for grouping and for a filter that needs more than two values.

city

A city name, alone rather than as a full address.

date

A day between two dates you choose, written as YYYY-MM-DD.

datetime

A day with a time, as an ISO 8601 stamp in UTC.

integer

A whole number inside a range, both ends included.

float

A decimal inside a range, rounded to the number of places you set.

boolean

True or false, with the share of true you ask for.

enum

One of the values in your own comma separated list.

lorem

A sentence of the lorem ipsum words, at the length you set.

slug

Lowercase words with hyphens, for a URL path or a file name.

url

An https address on example.com, with a path and a number.

ipv4

An address from the 192.0.2.0/24, 198.51.100.0/24 or 203.0.113.0/24 block, which is reserved for documentation.

hexColor

A six digit colour, ready for a swatch or a stylesheet.

creditCard

A number that passes a Luhn check, built on published test BINs. Not usable for a payment.

How it repeats

Three things make a run repeatable

01

One stream, drawn in order

Every value comes from a single pseudo random stream that the seed number starts. Cells are filled left to right, row by row, and each one takes what it needs. Nothing else, not the clock or the browser, has a say.

02

The schema is part of the order

Column names do not move the stream, but types, options, the row count and the null share do. Change one and the rows from that point differ, which is why the fingerprint in the output bar is worth keeping next to a fixture.

03

The fingerprint is the proof

Eight characters, computed from the file you would download. Two runs that print the same fingerprint produced the same bytes, on this machine or another one, this year or next.

What each format writes
Format Shape An empty cell Good for
JSONAn array of objects, indented, or NDJSON with one object per linenullA fixture a test reads, or a body to paste into a request
CSVA header row and one line per rowAn empty cell between commasA spreadsheet, a seed import or a data science notebook
SQLINSERT INTO with the column list, one statement or one per rowNULLFilling a local Postgres, SQLite or MySQL table
TSA type for the row and a typed constantnull, with | null in the typeA front end that needs mock data with the shape it expects

Questions

Is the data real?

No. Every value is generated from lists written for this page, or taken from ranges reserved for examples: names and cities are generic, mail is at example.com, phone numbers are in the 555-01xx band, addresses come from the documentation blocks, and card numbers sit on published test BINs. None of it belongs to a person.

Why does the same seed give the same rows?

All values come from one stream started by the seed, and each cell draws from it in the same order. The columns, their options, the row count and the null shares are part of that order, so two runs with the same settings write identical bytes.

What changes the output?

The seed changes every value. A column, its type, its options or the row count change the values from the first affected cell onward, which is why the fingerprint moves. Two files with the same fingerprint are the same file.

Are the card numbers usable?

No. They pass a Luhn check so a form or a validator can be tested, but they are built on test BINs and no bank issued them. Never put one into a real payment.

Can I use the output in a repository?

Yes. The rows are yours, with no attribution needed. They are made for tests, fixtures, demos and empty states.

Is anything sent anywhere?

No. The page generates, formats and downloads in the tab, and the content policy sets connect-src 'none', so no request could leave it. A draft of the columns stays in this browser so a reload does not lose them.

Why not use random values each time?

Because a test that fails once should fail again. A fixed seed turns a flaky fixture into a reproducible one: the failing row is a number you can share, not a screenshot.