Why every tool lists its limitations

Most tool pages carry a Limitations section below the workspace. It is there because a tool that quietly approximates is worse than one that says where it stops.

The kinds of limit

• Structural — the JWT decoder cannot verify a signature, because that needs a key it must never see.
• Approximate — domain parsing uses a short suffix list rather than the full Public Suffix List, so the split is a good guess.
• Lossy — JSON to CSV cannot represent nesting, and JSON to XML cannot distinguish a one-element array from a single value.
• Environmental — no tool can resolve a DNS record or fetch a remote schema, because there is no backend to do it.

Warnings in the interface

Some limits appear as notes under the output while you work, because they depend on what you did — sorting arrays reorders data that may have meaning, and turning off sanitising in the Markdown converter passes raw HTML through.

If a limit blocks you

Say so on the contact page. Some limits are deliberate and permanent; others are simply where we stopped.