Use the canonical 36-character UUID
The default 8-4-4-4-12 lowercase form contains 32 hexadecimal digits and four hyphens. Start here when an API, database, schema, or native UUID field expects conventional text.
Free online developer utility · no registration or login
Generate one random UUID v4 or a batch of up to 100 in your browser. Choose canonical, uppercase, GUID-braced, or compact display, then copy individual values or export the full list as TXT, CSV, or JSON with no registration or login.
UUID v4 workspace
Choose a practical batch size, display style, and file shape. Generation uses your browser Crypto API; no account or server generation request is required.
Common quantities
This page generates UUID version 4 only, with a maximum of 100 values per batch. GUID braces and compact output change the display, not the underlying identifier.
Set the options, then generate a fresh batch.
No UUIDs generated yet
The result list, per-value copy controls, version checks, and export preview will appear after generation.
Choose the representation first, then verify and export the exact batch you generated.
Enter 1–100 or select a common quantity. Choose canonical, uppercase, GUID-braced, or compact display and decide whether the copied or downloaded batch should be TXT, CSV, or JSON.
Generate fresh UUID v4 values, then review the actual result count, version-and-variant pattern check, and the number of distinct values in the current batch.
Use a row's copy control for one identifier, or copy and download the complete export representation shown in the result panel.
Pick the export shape that reduces cleanup in the database, test, spreadsheet, or script that receives the batch.
Changing case, braces, or hyphens changes the text representation, not the underlying random UUID. The receiver's documented format should decide which display you use.
The default 8-4-4-4-12 lowercase form contains 32 hexadecimal digits and four hyphens. Start here when an API, database, schema, or native UUID field expects conventional text.
The GUID-style option wraps an uppercase UUID in braces. It is useful when a .NET, Windows, or legacy interface documents that convention, but the braces are not universally accepted.
Compact output removes the four hyphens and leaves 32 lowercase hexadecimal characters. Some storage layers accept it, while strict UUID validators require the canonical separators.
The selected export format controls Copy all, the preview, and the downloaded filename so the saved file matches the structure you reviewed.
Plain text is convenient for seed lists, fixture columns, shell input, and manual imports that expect one identifier on each line.
CSV output adds a uuid header and quotes every value. It is a single-column table intended for spreadsheet review or a tabular import step.
JSON output is a valid array of strings with the selected UUID display style. Use it where a test fixture, configuration file, or script expects a JSON array.
Random UUID v4 values are useful opaque identifiers, but ordering, authentication, retention, and authorization are separate application decisions.
UUID v4 can label API resources, distributed records, requests, correlation events, and test fixtures without coordinating one shared sequence. Keep database constraints where duplicates cannot be accepted.
UUID v4 does not sort by creation time. If ordered database inserts or chronological identifiers matter, evaluate UUID v7 and the receiving system's support; this page intentionally generates v4 only.
A UUID can identify a session or token record, but it should not replace password hashing, secret generation, expiration, rotation, revocation, authorization, or secure storage.
The result panel reports evidence from the current batch while the page keeps important UUID and browser limitations visible instead of presenting randomness as a guarantee.
The page uses crypto.randomUUID(), which produces UUID v4 values from a cryptographically secure random number generator in supported secure browser contexts. It does not fall back to Math.random().
UUID v4 has a very large random space, but a collision remains possible in principle. Keep a uniqueness constraint and conflict handling whenever duplicate identifiers would be harmful.
After generation, the workspace checks each raw value for the expected v4 version and RFC variant pattern and compares the Set size with the requested batch. This verifies the current output, not every future UUID.
Direct answers about UUID v4, GUID formatting, bulk exports, collision risk, browser generation, and the difference between identifiers and secrets.
A UUID is a 128-bit identifier used to label information without coordinating one central counter. Its canonical text representation contains 32 hexadecimal digits in five hyphen-separated groups, for 36 characters in total.
This page generates UUID version 4 only through the browser Crypto API. UUID v4 uses 122 random bits after the standard version and variant fields are set; it does not embed a creation timestamp or device address.
Yes. Choose a whole number from 1 to 100 or use a common-quantity shortcut. Each result can be copied individually, and the full batch can be copied or downloaded as plain text, CSV, or JSON.
No random identifier is mathematically guaranteed never to collide. Correct UUID v4 generation provides an extremely large random space, but systems that require uniqueness should still use a unique constraint and handle a possible conflict.
GUID is terminology commonly used in Microsoft and .NET environments for the same 128-bit identifier family. This page's GUID-style option displays the UUID in uppercase braces; it does not use a different generation algorithm.
Yes. Choose standard lowercase, standard uppercase, uppercase with GUID-style braces, or compact lowercase without hyphens. These are display transformations of the same generated value, and the receiving system may still require canonical hyphenated text.
Use UUID v4 when you need a random opaque identifier without an embedded creation time. Evaluate UUID v7 when natural chronological ordering or database index locality matters. This page does not generate UUID v7.
Many databases support UUID values, and v4 can work when independently generated opaque keys are useful. Check the database's native UUID type, indexing behavior, storage format, and uniqueness constraints; consider a time-ordered alternative when write locality matters.
Do not treat an identifier as a complete authentication design. Passwords, session secrets, reset tokens, authorization, expiration, rotation, and secure storage need purpose-built controls even when a UUID labels the related record.
The current page calls crypto.randomUUID() and keeps the generated batch in the active browser tab. It does not send the values to an external UUID generation service or require an account; reset or close the tab to remove the current result from the page.
Hash values, reshape identifier lists, or inspect the JSON payload that uses them.
Use this hash generator to create a SHA digest from exact UTF-8 text or one local file. Choose SHA-256, SHA-384, SHA-512, or legacy SHA-1, then compare, copy, or download the result as hex or Base64 without sending the source to an external hashing service.
Open toolPaste one JSON object or an array of objects, or load a local .json file. Choose the delimiter, preview the rows and columns, and copy or download the CSV without registration or login.
Open toolPaste CSV or load one local .csv or .txt file, choose the delimiter and JSON format, then convert the header row and records into a JSON array. Quoted fields are parsed in your browser, values stay strings, and no registration or login is required.
Open toolPaste JSON or open a file to format, validate, beautify, or minify it. Choose indentation, review parser errors, and copy or download the result in your browser with no login.
Open tool