Signals used for detection
- Text syntax such as JSON, JWT, XML, HTML, CSS and URLs.
- Data URL MIME declarations and Base64 structure.
- Decoded magic bytes and container signatures when available.
Identify pasted Base64, JSON, JWT, XML, HTML, CSS, image, PDF, byte-array and encoded text, then open the most relevant converter or formatter.
The AI Format Detector helps identify pasted content before you choose a converter. It checks text structure, Data URI metadata, Base64-decoded signatures, byte arrays, hexadecimal bytes and common web file formats, then suggests the most relevant FileFlow Tool converter, formatter or analyzer.
Processed locally; nothing is uploaded.
Use this page when you are not sure whether copied content is Base64, a Data URI, byte array, hexadecimal bytes, JSON, JWT, XML, SVG, HTML, CSS, a URL or URL-encoded text.
The detector also inspects decoded file signatures for PNG, JPEG, GIF, WebP, BMP, TIFF, ICO, AVIF, HEIC/HEIF still images and sequences, PDF, ZIP, DOCX, XLSX, PPTX, fonts and common media containers.
Recommendations now consider both the detected format and how it was supplied. Base64 or Data URI AVIF can open Base64 to AVIF, AVIF file paths can open AVIF to Base64, and HEIC/HEIF bytes can open Bytes to Image while HEIC/HEIF file paths can open HEIC to PDF.
Structured web data can open JSON Formatter, JWT Decoder, XML Formatter, HTML Decode, URL Decode, Base64 Analyzer, Bytes to Image or the Text Tools hub.
Detection runs locally and does not upload the pasted input. The result combines MIME declarations, syntax checks, decoded magic bytes and confidence scoring.
Format detection is a best-effort recommendation. Files with missing headers, encrypted content, proprietary containers or incomplete data may still require the Base64 Analyzer or a specialised desktop application.
It recognizes Base64 and Data URIs, PNG, JPEG, WebP, AVIF, HEIC/HEIF still images and sequences, PDF and Office signatures, byte arrays, hexadecimal bytes, JSON, JWT, XML, SVG, HTML, CSS, URLs, URL-encoded text, fonts, archives and several common media containers.
Yes. For manageable inputs it decodes the Base64 locally and checks known magic bytes for image, PDF, archive, Office, font and media formats. Large inputs are identified structurally without loading the full payload into memory.
It can identify their declared MIME types and, when enough ZIP container data is available, look for Word, Excel or PowerPoint package entries.
No. Detection runs locally in your browser and does not upload pasted data to a server for analysis.
The detector shows a confidence score, explains the matching signal, lists secondary possibilities and links to the most relevant FileFlow Tool converter or formatter.
Yes. The detector is rule-based and works best when valid headers, MIME metadata or complete structured text are present. Truncated, encrypted or proprietary data may return a lower-confidence or generic result.
The detector classifies pasted data using syntax, declared MIME metadata and decoded byte signatures. It can recognize Base64 and Data URLs, byte arrays, hexadecimal bytes, JSON, JWT, XML, SVG, HTML, CSS, URLs and several common binary file containers without uploading the input.
When Base64 can be decoded safely, the tool checks magic bytes and container markers for formats such as PNG, JPEG, GIF, WebP, PDF and ZIP-based Office documents. Confidence is higher when multiple signals agree, while truncated, encrypted or proprietary payloads may remain generic or uncertain.
These links connect the current task with the closest reverse, inspection or format-specific workflow.
Inspect Base64 validity, MIME type, decoded size and known file signatures in more detail.
Format and validate JSON after the detector identifies structured JSON input.
Open the developer text-tool collection for JSON, JWT, XML, URL and HTML workflows.