Paste unfamiliar content to see a likely format and the evidence behind it. Open a suggested tool when you are ready to work with that format.
Runs locally in your browserSmart Paste uses conservative signatures and strict parsers where possible. Review the evidence before following a suggested workflow; detection is guidance, not a security verdict.
This page reads a payload you paste and names the format it most likely is, with a confidence figure, the evidence behind the guess, and links to the VoriTools tools that work with that format. Everything runs in the browser tab; the text is not uploaded, stored or opened.
Detection is heuristic. A strict JSON parse, a PEM header or a UUID pattern is a real test; the other rules look for shapes, such as two lines of key: value or the same comma count on every row. When the signals are weak the page says so with a lower confidence and plain text instead of a guess.
Unix timestamps in seconds (10 digits) and milliseconds (13 digits), ISO 8601 dates and date-times, JSON, JWT, cURL commands, URLs, HTML, XML, SQL, YAML, CSV, TSV, PEM blocks, UUIDs and Base64. Anything else falls back to plain text at 45%, which is the honest answer rather than a guess.
The rules run in a fixed order: timestamps and strict parsers first, then structural patterns such as HTML, YAML and delimited rows. A payload that satisfies more than one rule keeps the strongest match, so a JSON document containing commas is not reported as CSV.
Confidence is the strength of the matched signal, not a probability. A JSON object that parses without error is reported at 99%, a payload that only looks like a comma-separated table sits at 87%, and unrecognised text sits at 45%. A bare number such as 12345678901 is valid JSON and is reported at 62%, because the tool cannot know whether it is an ID, a phone number or a timestamp.
Detection is not a security verdict. The page reads the text and never executes, fetches or decodes it, and it does not send the content anywhere, so a JWT, a private key or a customer sample can be inspected in place. Decoding and validation belong to the linked tools.
The character, line and byte counters follow the textarea, and the preview shows the first 2,200 characters. In testing, a 600 KB JSON document, a 1.7 MB CSV export and a 2.2 MB text file were classified in about a quarter to half a second each on a desktop browser, and the cost grows with the payload.
Only the format label, the evidence and a plain-text preview are produced here: Base64 is not decoded, JWT signatures are not verified, and XML or SQL are not checked for correctness. Those steps are the reason each result carries links to the tool that performs them.