What does each thread contain?

Every thread has an id, a question-style title, a category, an author, multi-sentence body text, an upvote count, a view count, a reply count, a pinned flag, a creation timestamp and an array of reply objects. Each reply has its own id, author, body and upvotes.

How are the reply counts decided?

Each thread gets a random number of replies from zero up to the maximum you set, so some threads will have no replies and others will be near the cap, matching how real forums look. The replyCount field always equals the length of the replies array.

Are the timestamps realistic?

Yes. Thread creation times fall within the last ninety days of a fixed base date and are formatted as ISO 8601, so you can sort threads by recency just like a real forum.

Will the data fit my forum component?

It uses a conventional threads array with nested replies, the shape most discussion UIs model, so it loads into community-platform and forum components with little or no remapping.

Is anything sent to a server?

No. Threads are generated locally in your browser from a seeded random source. Nothing is uploaded, and identical settings reproduce identical data until you regenerate.

Forum Post Generator

Discussion data for community UIs

The Forum Post Generator creates fake discussion threads — question-style titles, body text, categories, vote and view counts, and nested replies. It is meant for prototyping community platforms and forum interfaces so you can build thread lists, detail pages and reply trees against realistic data before any backend exists.

How it works

You choose how many threads to create and a per-thread reply cap. For each thread the generator assembles a question-style title from verb and topic phrase pools, picks a category and author, and builds a two-to-four-sentence body from a pool of natural-sounding forum sentences. It then draws a random reply count between zero and your cap and builds that many reply objects, each with its own author, body and upvote tally. Upvotes, view counts and a low-probability pinned flag round out each thread, and a creation timestamp is placed within the last ninety days of a fixed base date.

A seeded pseudo-random source keeps a given configuration stable between renders while Regenerate advances the seed. The output is one object with a threads array; each thread carries its replies inline, so the structure mirrors a thread-with-replies API response and the replyCount field always matches the replies array length.

Tips and example

Set the reply cap to zero to generate a clean list of unanswered threads for testing an empty-state or a “no replies yet” view.
Raise the thread count to stress-test pagination and infinite-scroll on a forum index page.
The pinned flag appears on roughly one thread in ten, so you can build and test pinned-thread highlighting without editing the data.
Because timestamps are real ISO 8601 dates, sorting threads by createdAt gives a believable most-recent ordering.