Processing boundary
Input is processed only in the active browser tab's memory and is not sent to a ByteQuant server.
51
Code & file security
Local File Risk Pre-Scan
Inspects filename, size, magic bytes, MIME consistency, and risky text patterns in-browser without executing or uploading the file. It is not antivirus and cannot conclusively detect or clear new, packed, or complex malware.
✓ Free✓ No account✓ In-browser
Result
Your result will appear here.
Persistent storage
Input and output are not stored. The optional usage counter keeps only tool identity and count, never content.
Verification
Output comes from disclosed rules or browser APIs and needs independent review before high-impact use.
A result in three steps
- 01
Choose only a file you are authorized to inspect.
- 02
Run the size-bounded local scan; the file is never opened or executed.
- 03
If findings are suspicious, isolate the file and verify with a current professional security product.
When is this tool useful?
- ✓ Initial triage of a downloaded file
- ✓ Extension/signature mismatch checks
- ✓ Macro and script indicator search
Important limitation
Automated output is a preliminary assessment. Do not use it alone for legal, financial, medical, or security-critical decisions.
LEARN THE WORKFLOW
Guides for this tool
Browser File Risk Scanning: Magic Bytes, Double Extensions, and Real Limits
Inspect extension, signature, macro, and bounded content signals without executing a file—and do not confuse triage with antivirus verification.
Read guide →PWA Installation and Offline Caching: A Privacy-First Design Guide
Understand web app installation, the service worker lifecycle, and cache boundaries that keep sensitive inputs out of persistent storage.
Read guide →ABOUT THIS TOOL
Frequently asked questions
Does this tool send input to a server?+
No. Processing runs in this browser tab. Data leaves the page only when you choose to copy or download the result.
Is the result definitive?+
The tool produces consistent output from disclosed rules and browser APIs, but context, data quality, and method limitations can affect it. Verify high-impact decisions.
Is input saved?+
No. Tool input is not persisted. With consent, only tool identity and usage count may be kept on this device for personal shortcuts.