Understand invisible Unicode characters

When is this relevant?

This check is relevant whenever a file arrives unexpectedly, comes from email, messenger, download portals, or AI workflows, or should be cleaned before forwarding.

It matters most for urgent-looking files, unknown senders, or files that would otherwise be opened in apps that interpret active content.

What risks can exist?

Common risks include misleading filenames, active content, external loading targets, hidden metadata, suspicious archive paths, invisible Unicode characters, and prompt instructions for AI systems.

The exact assessment depends on the file type. ScanBeforeOpen therefore shows signals and recommendations, not a complete safety promise.

How does ScanBeforeOpen help?

The file is checked locally in the browser. There is no upload and no execution of the original file.

The result starts with a plain recommendation. Technical details, safe preview, and cleaned exports appear only where they make sense for the file type.

Exactly what is checked

Extension, magic bytes, filename, size, and matching content patterns are checked locally.

Findings are weighted by risk, repetition, and category so normal hints do not escalate unnecessarily.

Preview and clean export appear only where they are technically sensible.

Common characters

Zero Width Space, Word Joiner, Soft Hyphen, No-Break Space, and bidi controls can alter display or readability.

In filenames they can hide extensions or visually reorder text.

Human vs machine

A useful view shows what a person sees and what the system reads.

Visible control character markers make deception easier to spot.

Practical response

Rename suspicious files before forwarding them.

Do not directly open files with bidi or zero-width tricks from unknown sources.

A safer everyday review flow

Start with the source: Was the file expected, does the context make sense, and can the sender be confirmed through a second channel? Technical findings matter more when the social context is weak.

Then review filename, extension, size, magic bytes, and visible warnings. Do not open the original in another app while you are still assessing it.

If you need to share the content, prefer a cleaned export or a report over the original file. That reduces metadata, active content, and unintended remote-loading behavior.

When to escalate

After critical findings or several high-risk findings, do not open the file directly. This is especially important for resumes, invoices, contracts, archives, and files framed as urgent.

In organizations, a red result should go to IT support or security owners. Individuals should use professional antivirus or an isolated environment when uncertainty remains.

A green result only means no obvious known risk patterns were found. It is not a guarantee and does not replace approval for confidential content.

Document without spreading risk

When reporting a suspicious file, capture source, filename, time, and findings. Avoid uploading the original file into chats or unknown online services.

Screenshots or a local security report are often enough to decide the next step without redistributing the original.

Practical checklist

• Check bidi controls
• Mark zero-width characters
• Detect mixed scripts
• Find false dot characters
• Compare technical extension

Clear limits

Homoglyph detection is heuristic and may mark legitimate multilingual names.