What is this, and what can I do with it?
Paste a token, a config, an error message, a schedule, an address — or drop an image, a PDF or a spreadsheet — and get told what it is and which of Zellio.io's tools does the job, opened with it already loaded.
How the detection works
There is no guessing model behind this page. Each recognition is one of the site's own parsers saying yes: a paste is JSON because the formatter's validator accepts it, a cron expression because the schedule parser does, a subnet because the calculator can compute its range. That is why the verdict here never disagrees with the tool it sends you to, and why an invalid input is reported with the same message the tool would show — the position of the bad character in a JSON document, the field a cron expression gets wrong.
Files are identified from their first bytes. A PNG begins with a fixed signature, a PDF with “%PDF”, an Office document is a ZIP archive with a particular name, and an SVG is XML with an svg root. The extension is consulted only when the bytes are ambiguous, which means a renamed file is still identified correctly and a file that lies about its type is not trusted.
Error messages are the one case with a search behind them. The Errors collection in the Library is indexed by the message text, so a pasted stack trace is reduced to its most searchable part — an error code such as EADDRINUSE, an exception name with its message — and matched against it. A hit takes you to a page that explains the message, its usual causes and the checks that tell them apart.
Questions
- What can it recognise?
- Pasted text: JSON (valid or not, with the error), JSON Web Tokens, URLs, CSV, cron expressions, regular expressions, IPv4 addresses and CIDR blocks, MAC addresses, hex colours, Unix timestamps, UUIDs, hash digests, Base64, error messages and stack traces, HTML, Markdown, YAML, SQL, and text carrying invisible or look-alike characters. Files: images, SVG, PDF, Office documents, ZIP archives, CSV, JSON and plain text, identified from their first bytes rather than their extension.
- Where does what I paste go?
- Nowhere. Detection runs in this tab against the same parsers the tools use. When you pick a tool, the text travels inside the link as a fragment the server never receives, exactly as the tools' own share links work. A file is handed over in memory to the tool page you open, and is gone when you leave.
- It says my error is not in the Library. What now?
- The Errors collection is indexed by message text and grows with every wave of entries. Browse it by ecosystem, or paste the message into the character inspector first — an “unexpected token” error is often a hidden character in a config file rather than a mistake in the visible text.
- Why does a file open in the tool with nothing loaded?
- Nine tools accept a file handed over directly: the compressor, cropper, EXIF tool, vectoriser, palette extractor, OCR, PDF toolkit, document privacy inspector and SVG optimiser. The rest are linked with a note to drop the file again there; the hand-off also expires after a minute, so a long detour resets it.