File Converter

File Converter is a local conversion workbench for researchers who need to transform evidence-adjacent material without sending it to a third-party conversion service. It handles byte encodings, text encodings, and common structured-data representations such as JSON, NDJSON, CSV, TSV, and Markdown tables. The tool is useful for preparing report snippets, normalizing vendor-provided tabular data, decoding compact payload representations, or creating explicit JSON envelopes around binary-safe content.

This is not a universal document transcoder. Formats such as Office documents, PDFs, archives, images, executable containers, and macro-bearing files require specialized parsers or renderer sandboxes. Those formats are intentionally outside this browser tool until a separate review determines that a specific WASM-backed parser is appropriate, bounded, and maintainable. The goal is to make safe conversions reliable before attempting broad binary-document support.

Local Processing Boundary

This tool runs in the browser. It does not upload input, call a backend API, or store values unless the page explicitly says otherwise.

Converter runs entirely in the current browser tab. It is designed for byte, text, and structured-data transformations that can be handled safely without invoking external services or executing file content.

Conversion Boundary

This workbench is intentionally conservative. It can convert selected files or pasted text between byte encodings, data URLs, JSON envelopes, delimited tables, NDJSON, JSON, TSV, CSV, and Markdown tables. It does not attempt Office, PDF, image, archive, or executable transcoding because those formats require larger parsers, renderer behavior, or WASM sandboxes that need separate review.

Bytes ⇄ Base64/Base64URL/Hex/Data URLText ⇄ UTF-8/Percent EncodingJSON ⇄ NDJSON/CSV/TSV/MarkdownCSV/TSV ⇄ JSON Objects or Rows

Input

Input FormatRaw Bytes / Selected FileUTF-8 TextBase64Base64URLHexData URLPercent-Encoded TextJSONNDJSONCSVTSVByte input can be emitted as text-safe encodings and JSON envelopes.Selected FileMaximum input: 12.0 MiB.

Line EndingsPreserveLFCRLFCROutput MIME Hint

Output

Output FormatUTF-8 TextBase64Base64URLHex CompactHex GroupedData URLJSON EnvelopeJSON Byte ArrayJSON PrettyJSON MinifiedNDJSONCSVTSVMarkdown TableByte representation. Unsupported pairings fail closed with an explanation.

Working limit: 12.0 MiB

Supported Transform Families

• Raw bytes to Base64, Base64URL, grouped hex, compact hex, data URL, JSON envelope, or JSON byte array.
• UTF-8 text to normalized line endings, percent-safe text forms, and byte-safe encodings.
• JSON and NDJSON to pretty JSON, minified JSON, NDJSON, CSV, TSV, or Markdown table output.
• CSV and TSV to JSON row arrays or field-name objects when the first row is treated as headers.
• Pasted data URLs and encoded strings back into local byte/text representations.

Data Handling

• Input is processed in the current browser tab after explicit user action.
• No input or output is uploaded, transmitted, indexed, logged, or sent to a backend API.
• The tool does not use persistent browser storage, session storage, IndexedDB, service workers, or telemetry.
• Downloaded artifacts are generated with temporary browser objects and are released after the download action.
• Input size is intentionally bounded because browser conversion currently uses whole-buffer processing.

Boundary

This tool is not a sanitizer, malware scanner, document repair system, archive extractor, image converter, PDF renderer, Office parser, or forensic evidence vault. It does not validate whether converted data is safe to publish, safe to execute, or safe to import into another system. Treat output as a representation change only. When handling sensitive evidence, perform the conversion inside the same review environment where the material is already authorized to exist.

Future binary-format support must be added through an explicit tool contract, dependency review, file-size bound, and test corpus. A broad converter that silently accepts every file type would be less trustworthy than a narrower tool that fails closed.