Build synthetic rows for spreadsheets, seeds, and API mocks — names, emails, fictional phone patterns, companies, titles, addresses, usernames, and placeholder passwords. Generation runs only in your browser, like APK Analyzer and APK String Extractor: nothing is sent to DroidXP. After exporting JSON, you can pretty-print it with the JSON Formatter or track real tasks in Todo List.
Columns: first_name, last_name, email, phone, company, job_title, address, city, state, zip, username,
password. Phones use fictional 555-style patterns; emails use reserved-style domains — not for real outreach.
Use generated rows for local development, UI mocks, and test databases — the same “nothing leaves the tab unless you copy it” idea as APK String Extractor. Do not present this data as factual or use it to contact anyone.
Random assembly runs in JavaScript; optional row count and format preferences may be stored in localStorage. DroidXP does not receive your generated output.
No. Random assembly runs only in your browser — the same local-only stance as APK Analyzer and APK String Extractor. Optional defaults may be saved in localStorage on your device only.
No. Names and details are picked from small built-in word lists and random numbers — purely synthetic for demos and tests, not sourced from public records.
No. Emails use reserved-style domains; phones use fictional 555-style patterns. Use only in dev, QA, or staging — never for contacting real users.
They are random-looking but not from a vetted password generator workflow — treat them as disposable placeholders, not secrets for real accounts.
UUID Generator emits standards-based identifiers. This tool builds broader fake person-style rows for spreadsheets and API mocks.
The same small dictionaries are reused; collisions are possible. Regenerate or post-process in your own pipeline if you need strict uniqueness.
The UI caps batch size to keep the page responsive — very large outputs may still feel slow on low-memory devices.
After the page loads once, generation works offline because logic is client-side — similar to offline-friendly APK parsing.
CSV fields are escaped when they contain commas, quotes, or line breaks so common spreadsheet imports behave.
You are responsible for how you use synthetic data in your organization — this tool does not provide legal or compliance advice.