Disclaimer

The tools and reference content on Zellio.io are provided as is, for general use, without warranties of any kind. That sentence appears on every site of this sort, so the rest of this page does the more useful job: naming the specific places where the output is approximate, and where you should check before relying on it.

Tools that are approximate by nature

Optical character recognition reads text from an image by inference, not by reading a text layer. Accuracy depends on resolution, contrast, typeface and skew, and it degrades on handwriting, low-contrast scans and unusual scripts. Treat the output as a first draft to proofread, never as a faithful transcript.

Face detection in the Image Redactor finds probable faces. It misses some, and it occasionally boxes something that is not a face. If you are redacting an image because the identities in it matter, check every region it proposed and add the ones it did not before exporting.

Background removal and image compression are lossy operations judged by eye. A compressed file that meets a target size has, by definition, discarded detail to get there.

Privacy tools have limits worth knowing

The Document Privacy Inspector and the EXIF remover strip metadata a file carries alongside its visible content. They cannot remove information that is part of the content itself — a name typed into the document, a face in the photograph, a reflection in a window, a watermark burned into the pixels. A file that has been cleaned is not the same thing as a file that is safe to publish, and the tools say so where it matters.

A matching hash tells you two files are byte-identical. It does not tell you the file is safe, that the download was not tampered with before the checksum was published, or that the publisher is who they claim to be.

Patterns, commands and formulas

Library entries are checked by execution rather than by proofreading — regular expressions are run against their own listed examples before each release, and cron expressions are parsed. That catches errors of fact; it cannot know your data. A pattern that is correct in general may still be wrong for your input, and the honest limits are listed on each entry for that reason. Test against your own data in the linked tool before putting anything into production.

Shell commands are shown with an explanation of what each part does precisely so you do not run them on trust. Anything destructive — deleting, killing processes, overwriting — should be understood before it is pasted into a terminal, especially on a machine you share or a server you cannot easily restore.

Templates are drafts, not advice

The email, document and invoice templates in the Library are starting points written for general situations. Nothing here is legal, financial, tax, medical or employment advice, and no template has been reviewed for any particular jurisdiction. Where a document has legal or financial consequences — a contract, an invoice that must satisfy tax rules, a letter about employment — have it reviewed by someone qualified in your jurisdiction before you send it.

Your browser is the limit

Because everything runs locally, capacity is set by your device rather than by a server. Very large files can exhaust available memory, and a tab that runs out of memory ends the operation without warning. Results can also differ slightly between browsers where they implement an image or text feature differently.

No liability

Zellio.io and its authors are not liable for any loss or damage arising from use of, or inability to use, the tools and content on this site. This does not affect rights you have under law that cannot be excluded.

External links

This site links to third-party documentation and specifications where they are the authoritative source. We are not responsible for the content, accuracy or practices of those sites.

Found something stated wrongly? Corrections are welcome and are made promptly — see the contact page.