What does the unicode invisible character inspector do?
Paste text to expose zero-width characters, non-breaking spaces, soft hyphens, byte-order marks, variation selectors, bidirectional controls, unusual whitespace, code points, and exact positions. The immediate result is an annotated Unicode character inventory and cleaned text option. That makes the tool useful when a focused question needs an answer before a file is handed off, a campaign is trafficked, or a production workflow begins.
The scope is intentionally narrow. It is designed for checking one set of strings, localization files, or copy constraints, not for replacing the complete production process. A useful result should make the next decision clearer while leaving the original file, design, or workflow under the user’s control.
Text is inspected locally and is not sent to Hypermatic. Local processing reduces unnecessary data exposure, but it does not remove the need to follow the privacy, confidentiality, and retention requirements that apply to the source material.
How should the unicode invisible character inspector be used?
Start with the same input that will be used in production whenever possible. Draft content, substitute files, and approximate dimensions can be useful during exploration, but the final check should use the actual export, final copy, destination, or supported range.
Work through the steps in order and keep the generated result beside the source. If the result identifies a warning, decide whether it is a real production problem, an acceptable tradeoff, or a limitation of a browser-based inspection before changing the underlying work.
- Paste the problematic interface, document, or localization text.
- Inspect every invisible or control character with its Unicode code point, name, position, and risk category.
- Copy a cleaned version deliberately and confirm that required language direction or typography was not removed.
How should the result be interpreted?
A browser tool can make measurable signals visible, but it cannot reproduce every application, platform, rendering engine, policy, or team constraint. Treat the report as evidence for a decision rather than a universal guarantee. The strongest verification is the source content system, linguistic review, runtime placeholders, and the final Figma layouts.
Pay particular attention to edge cases that are easy to miss during a quick check: unusual fonts, long or localized content, hidden metadata, external dependencies, different aspect ratios, browser-specific behavior, and last-minute source changes. Re-run the tool whenever the production input changes materially.
- Bidirectional controls can be legitimate in mixed-direction text, so do not remove them blindly.
- Non-breaking spaces and soft hyphens may be intentional typography rather than corruption.
- Compare source and destination systems because copying through editors can insert or strip controls.
Common questions about unicode invisible character inspector
Which invisible characters are detected? The inspector covers common zero-width characters, bidi formatting and isolation controls, non-breaking and unusual spaces, soft hyphens, byte-order marks, variation selectors, and control characters.
Can it safely remove every invisible character? No. It produces a configurable cleaned copy, but some controls are required for correct language direction, emoji presentation, typography, or line breaking.
Is the unicode invisible character inspector free? Yes. You can use it without an account or signup. The focused result is generated directly in your browser.
When does CopyDoc become the better workflow?
The free tool is the right choice for a quick individual check, calculation, preview, or template. It remains useful even if the task only occurs once and no broader production workflow is needed.
CopyDoc becomes more practical when the same job turns into syncing, localizing, importing, and updating content across complete Figma designs. At that point, keeping the work close to the Figma source reduces repeated exports, copy-and-paste steps, inconsistent decisions, and handoff drift.
Before adopting any workflow, compare the time spent on the recurring manual process with the setup and review required by the tool. The goal is not to add another application; it is to remove repetitive work while preserving the quality checks that still need human judgment.