Frequently Asked Questions

Most FileFlow converters process files and pasted data locally in your browser. Your input stays on your device unless a specific page clearly states otherwise.

No. Base64 is an encoding method, not encryption. Anyone with the encoded string can decode it, so do not use Base64 to protect secrets.

Local conversion uses browser memory and CPU. Large Base64 strings, high-resolution images and multi-page PDFs can require substantial memory, especially on mobile devices.

Current versions of Chrome, Edge, Firefox and Safari provide the best support. Private browsing, strict browser extensions or low available memory can affect downloads and large conversions.

It recognises Base64 and Data URIs, byte arrays, hexadecimal bytes, JSON, JWT, XML, SVG, HTML, CSS, URLs, URL-encoded text, common image signatures, PDF, ZIP-based Office files, fonts and several media containers.

Yes. For manageable inputs it decodes the data locally and checks magic bytes for formats such as PNG, JPEG, GIF, WebP, BMP, TIFF, ICO, AVIF, HEIC, PDF, ZIP, fonts and media files.

Some inputs match several layers. A PNG Data URI, for example, is simultaneously a Data URI, Base64 data and a PNG image. The detector ranks the strongest match and shows secondary possibilities.

No. It is a lightweight, rule-based detector that runs locally. It combines syntax checks, MIME declarations, decoded signatures and confidence scoring without sending your data to an AI API.

A Base64 image is binary image data represented as text. It commonly appears in HTML, CSS, JSON, API responses and email templates.

No. Encoding does not alter the source pixels. It changes only the representation, although the Base64 text is usually about 33% larger than the original binary file.

The image tools cover common browser formats such as PNG, JPG/JPEG, GIF, WebP, SVG, BMP, TIFF, ICO and AVIF. Individual converter pages may support a smaller, clearly stated set.

Use Bytes to Image when the values represent an image. It accepts decimal arrays, Uint8Array, Node.js Buffer output and hexadecimal bytes, then validates the detected image signature before previewing it.

The Base64 may contain a PDF, archive, font, text file or corrupted image rather than a supported image. Base64 Analyzer or AI Format Detector can inspect the decoded signature first.

FileFlow includes image-to-PDF, PDF-to-image, merge, split, reorder, rotate, page deletion and extraction, page numbers, watermarking, signing, metadata editing, compression, protection and document conversion tools.

Yes. Dedicated JPG, JPEG, PNG, WebP and HEIC pages are available, while Image to PDF supports mixed common image inputs.

Yes. PDF to JPG, JPEG, PNG, WebP and the general PDF to Image tool render document pages as downloadable images.

Protected PDFs may require a valid password before page access. Some files use unsupported encryption, damaged cross-reference tables or unusual embedded content that browser libraries cannot process reliably.

Not always. Browser conversion prioritises privacy and convenience. Complex layouts, uncommon fonts, advanced forms, macros and proprietary document features may render differently.

You can format, beautify, minify, validate and view JSON. Invalid syntax produces a readable error rather than silently modifying the data.

The JWT tools decode and inspect token structure and claims. Decoding alone does not prove authenticity; cryptographic signature verification requires the correct secret or public key.

FileFlow includes XML formatter, validator and minifier pages, HTML encode/decode tools, and URL encode/decode tools for query strings and web text.

Local processing reduces upload exposure, but you should still follow your organisation’s security rules and avoid pasting secrets, private keys, credentials or regulated data into any unapproved browser environment.