Extract every detail from any file — size, type, hashes, timestamps, magic bytes
This tool reads files using the File API's arrayBuffer() method, accessing raw binary data without uploading. Magic byte detection compares the file's hex header against a database of known file signatures (JPEG: FF D8 FF, PNG: 89 50 4E 47, PDF: 25 50 44 46, etc.) — this reveals the true file type even when the extension is misleading. Cryptographic hashes are computed via the Web Crypto API's crypto.subtle.digest(), producing standard checksums identical to those from shasum or certutil commands.
Real-world use cases:
This tool is part of the FAK LAB ecosystem, founded by Faizan Ahmad Khan Khichi. Files are read entirely in your browser's memory using the File API. No file data, content, or hash values are ever transmitted to any server. The tool cannot access files you don't explicitly select — there is no background scanning, no file indexing, and no remote storage of any kind. Your files remain 100% on your device.
Magic bytes (file signatures) are the first few bytes of a file that identify its true format. A JPEG always starts with FF D8 FF, a PDF with %PDF (25 50 44 46), and a ZIP with PK (50 4B). This is more reliable than file extensions because anyone can rename a .exe to .jpg — but the magic bytes reveal the truth. Security tools, operating systems, and forensic software all use magic bytes for file identification.
The MIME type comes from the browser's guess based on the file extension. The detected type comes from analyzing actual file content (magic bytes). If someone renames "malware.exe" to "photo.jpg", the MIME type would say "image/jpeg" (extension-based) while detected type correctly identifies "Windows EXE/DLL" (content-based). Trust the detected type.
The Web Crypto API is hardware-accelerated on most modern devices. For files under 100MB, hashing typically completes in under 2 seconds. For multi-gigabyte files, it may take 10-30 seconds depending on your device's processing speed and memory. The entire file must be read into memory, so very large files on low-RAM devices may cause browser slowdowns.