Questions about ConvertAnyFile.
How browser-first conversion works, why each category has safety limits, what the live Image, Data, Archive, and Subtitle engines can do, and what users should expect from output fidelity and privacy.
The important answers in one place.
ConvertAnyFile follows a simple rule: explain what each local engine can do, do not publish placeholder converters, and keep the batch workflow understandable when something goes wrong.
Image, structured Data, Archive, and Subtitle are production converter categories with separate validation, safety policies, and output contracts.
- Live converters process supported file bytes in the browser session.
- The shared workspace supports batches, cancel, recoverable retry, individual downloads, and ZIP results.
- Each category validates its own inputs instead of trusting filenames blindly.
- Safety limits protect browser memory and CPU rather than protecting a conversion server.
Platform questions
Accounts, local processing, batches, cancellation, failures, and how the platform grows without duplicating the converter shell.
Are my files uploaded to a conversion server?
For the browser-first converters currently available on ConvertAnyFile, supported files are processed on your device. The live Image, Data, Archive, and Subtitle categories do not require source-file contents to be uploaded to a ConvertAnyFile conversion server.
Do I need an account?
No. The core browser converters are designed to work without registration, sign-in, or a cloud project.
Can I convert multiple files at once?
Yes. The shared batch workspace provides per-file status, individual downloads, append-by-drag, failure isolation, and ZIP download for successful results. Category-specific limits still apply.
Why are there batch limits?
Local conversion uses the memory and CPU of your device. Each category defines limits that reduce the chance that unusually large files, expanded archives, decoded images, parsed data, or pathological cue counts make the browser tab unstable.
What happens if one file fails?
A failed file does not stop the rest of the batch. Retry is only offered for failures that may recover; deterministic invalid or unsupported files are not placed in a pointless retry loop.
Can I cancel a conversion?
Yes. Cancelling resets the active category engine. Results that already finished remain available, and unprocessed files can be converted later.
Does ConvertAnyFile change my original file?
No. Conversion creates a new downloadable output. Your original local file is not overwritten by the website.
Why can the first conversion take longer?
Some categories start a browser worker or load a WebAssembly engine only when needed. First use can include engine startup and caching work; later conversions in the same environment may start faster.
Which converter categories are available?
Images, structured Data, Archives, and Subtitles are live. Subtitle supports SRT, VTT/WebVTT, ASS, SSA, and SBV input; SRT, VTT, SBV, and TXT output; full-file preflight analysis; timing-shift controls; formatting cleanup; and transcript export options.
Why not process every file type on a server?
Server conversion can be useful for heavy or specialized workflows, but it adds upload time, temporary storage, cleanup, and infrastructure cost. ConvertAnyFile prefers browser-first processing when the user experience and fidelity contract can be made dependable.
Image converter questions
Image formats, quality settings, transparency, RAW files, memory use, and what conversion can or cannot improve.
Which image formats can I add?
The image engine recognizes 57 filename extensions across common raster, specialist, legacy, and camera RAW families. A file still has to pass signature validation and runtime decoder checks before it is treated as supported.
Which image formats can I convert to?
The production output catalog contains 16 formats: JPG, PNG, WebP, AVIF, TIFF, GIF, BMP, ICO, JXL, JP2, HDR, EXR, PCX, TGA, QOI, and PNM. The browser only shows a format when the packaged ImageMagick runtime also reports that encoder as writable.
Why can I open HEIC but not choose HEIC as an output?
Input and output capability are separate. The current packaged WASM runtime can expose HEIC/HEIF decoding for compatible source files, but its runtime writer scan does not expose a HEIC encoder. ConvertAnyFile therefore keeps HEIC as an input family and does not advertise HEIC output in this release.
How many images can I convert in one batch?
The current safety policy allows up to 50 files, up to 75 MB per file, and up to 300 MB total input per batch. You can also drag or add more files after the initial batch as long as the limits are not exceeded.
Why do some outputs show a quality control?
Lossy outputs such as JPG, WebP, AVIF, JXL, and JP2 can use an encoder quality setting. Formats without a comparable quality control do not show the slider.
Does converting JPG to PNG restore lost detail?
No. Changing the container format cannot restore image detail already lost through earlier JPEG compression.
What happens to transparency when converting to an opaque format?
Outputs without a useful alpha channel use a deterministic white background instead of leaving transparent pixels undefined. JPG is the most common example.
What happens to animated, multi-page, layered, or multi-size files?
The current product creates one output image per input file. Animated GIF/WebP, multi-page TIFF, layered sources, and multi-size icon containers are therefore flattened to a single image representation. ICO inputs use the best available embedded icon frame when possible.
Can I convert HEIC photos to JPG?
Yes when the runtime can decode the specific HEIC file. HEIC to JPG is useful for broader compatibility with upload forms, older software, and general sharing.
Can a RAW camera file fail even if its extension is recognized?
Yes. RAW families vary by camera and decoder requirements. Recognition of the extension does not guarantee that the packaged browser runtime can decode every variant, so RAW remains a best-effort input path until more real-camera fixtures are certified.
Why can a small image file still use a lot of browser memory?
Compressed file size and decoded pixel memory are different. A very high-resolution image can expand to hundreds of megabytes after decoding even when the source file is only a few megabytes on disk. The image engine rejects extreme dimensions or estimated decoded memory before conversion.
Can I download all successful images together?
Yes. Successful batch results can be packaged into a ZIP while failed files remain isolated from the rest of the batch.
Does converting an image make it higher resolution?
No. Format conversion changes encoding or container representation. It does not add genuine source detail or automatically increase useful resolution.
Data converter questions
CSV and TSV headers, JSON nesting, JSONL/NDJSON, UTF-8, output controls, and structured-data batch limits.
Which structured data files are supported?
The production data engine accepts CSV, TSV, JSON, JSONL, and NDJSON. NDJSON is treated as the JSON Lines input family. Files must contain valid UTF-8 text.
Which data formats can I convert to?
The current production outputs are CSV, TSV, JSON, and JSONL. They cover tabular exchange, normal structured JSON, and line-oriented JSON workflows without requiring a server upload.
How are CSV and TSV headers handled?
The first row is treated as the header. Empty headings receive generated names such as column_1, and duplicate headings are made unique so JSON objects do not silently overwrite fields.
Does CSV to JSON automatically convert numbers or dates?
No. CSV and TSV cell values remain strings. Avoiding type guessing protects identifiers, leading zeros, date-like text, and codes from silent changes.
How are nested JSON objects converted to CSV or TSV?
Nested plain objects are flattened with dot notation, for example profile.city. Literal dots and backslashes in source property names are escaped so they cannot collide with paths created from nested objects. Arrays and other complex values are serialized as JSON text inside a cell.
How are precision-sensitive JSON numbers handled?
ConvertAnyFile rejects unquoted JSON numbers that would be rounded by the browser, including integers outside the safe range and high-precision decimals or exponents that cannot round-trip without changing value. Exact identifiers, money values, or other precision-sensitive numbers should be represented as JSON strings before conversion.
What is the difference between JSONL and NDJSON here?
For conversion purposes they are aliases. Each non-empty line must contain one complete valid JSON value, and blank lines are ignored.
Can CSV fields contain commas, quotes, or line breaks?
Yes. The delimited-text parser supports quoted fields, escaped double quotes, delimiters inside quoted fields, and embedded CRLF or LF line breaks.
Why is there a UTF-8 BOM option for CSV and TSV?
Some spreadsheet workflows benefit from an explicit UTF-8 BOM for encoding detection. It is off by default because plain UTF-8 is the cleaner general-purpose output.
What are the data batch limits?
The data category allows up to 50 files, 20 MB per file, and 100 MB total input per batch. Structured text can expand substantially while parsing, so local processing still needs memory safeguards.
Are my CSV or JSON files uploaded?
No upload step is required for the current data converter. Validation, parsing, conversion, and serialization run in the browser session, with the heavier conversion work placed in a browser worker.
Archive converter questions
ZIP, 7Z, RAR, TAR, TAR.GZ, GZIP, password protection, browser limits, and fail-closed archive safety.
Which archive formats can I add?
The Archive converter accepts ZIP, TAR, TAR.GZ/TGZ, GZIP/GZ, 7Z, and supported RAR4/RAR5 input. 7Z and RAR use a lazy-loaded browser WebAssembly decoder.
Which archive formats can I convert to?
Certified public Archive outputs are ZIP, TAR, and TAR.GZ. 7Z, RAR, and generic GZIP are input-only in the current release.
Are password-protected archives supported?
No. Password-protected or encrypted ZIP, 7Z, and RAR inputs are rejected instead of producing an incomplete result.
How does Archive protect against unsafe files?
The engine validates signatures and container integrity, rejects unsafe or duplicate paths and unsupported special entries, and enforces entry-count, per-entry, source-size, and expanded-size browser limits.
Why can an archive fail even when it is small?
Compressed size can be much smaller than expanded content. A small archive can contain a very large file tree or use unsupported metadata or compression features, so the browser applies limits while decoding rather than trusting compressed size alone.
Subtitle converter questions
SRT, VTT/WebVTT, ASS, SSA, SBV, preflight parsing, timing shift, formatting cleanup, transcript export, encodings, and browser limits.
Which subtitle formats can I add?
The Subtitle Converter accepts SRT, VTT/WebVTT, ASS, SSA, and SBV. Before a file becomes Ready, the complete subtitle is parsed in a local worker so malformed later cues are caught during admission rather than after conversion starts.
Which subtitle formats can I export?
Supported outputs are SRT, VTT, SBV, and plain TXT. The public catalog exposes 17 useful cross-format routes. ASS and SSA remain input-only because their richer styling, positioning, karaoke, and effect model cannot be recreated faithfully by the simpler outputs.
What does the preflight analysis show?
Accepted files report cue count, timeline end, detected text encoding, and a flag when richer formatting or WebVTT metadata is present. This is calculated locally from the full file before it enters the ready queue.
Can I shift subtitle timing precisely?
Yes. Timing shift accepts an exact millisecond offset from -600000 to +600000 ms, so values such as +1350 or -780 work across the whole batch. If a negative shift would move any cue before 00:00, conversion fails instead of silently clipping the timestamp.
Can I remove subtitle formatting?
For SRT, VTT, and SBV output you can enable Plain text only to remove inline formatting from cue text. TXT output is always plain readable text and removes subtitle markup automatically.
What TXT transcript options are available?
TXT can export dialogue with no timestamps, each cue start time, or complete start-to-end ranges. Cue spacing can use a blank line or a single line break, and LF/CRLF plus optional UTF-8 BOM are available for downstream compatibility.
Are my subtitle files uploaded?
No. Preflight analysis, parsing, timing transforms, text cleanup, and serialization run inside a browser worker. The selected subtitle is not sent to a ConvertAnyFile conversion server.
What happens to ASS or SSA styling?
Dialogue start time, end time, and readable text are carried into the target. ASS/SSA override tags, named styles, fonts, colors, positioning, karaoke instructions, drawing commands, and effects are intentionally not preserved in SRT, VTT, SBV, or TXT output.
What happens to WebVTT metadata?
SRT, SBV, and TXT cannot represent WebVTT STYLE, REGION, NOTE, X-TIMESTAMP-MAP, cue positioning, or other VTT-only metadata. A no-transform VTT-to-VTT export preserves the original validated WebVTT body by default; applying timing or text transforms rebuilds cues and cannot guarantee document-level metadata preservation.
Which text encodings are supported?
UTF-8 is preferred. UTF-8, UTF-16LE, and UTF-16BE BOMs are recognized. Files without a BOM are decoded as strict UTF-8 first, with Windows-1252 as a compatibility fallback. The detected encoding is shown in queue metadata; generated text output is UTF-8.
Why does the Subtitle converter have file-size limits?
Subtitle conversion is lightweight, but complete preflight parsing and unexpectedly large timed-text files can still consume browser memory and CPU. Current limits are 50 files, 5 MB per file, 50 MB total input, and a 100,000-cue parser guard.
Use the category that matches the source file.
Image, Data, Archive, and Subtitle have separate validation and transformation rules, but share the same local queue and download experience.