Free online archive converter for 7Z, RAR, ZIP and TAR.

Open 7Z and RAR or repackage ZIP, TAR, TAR.GZ, TGZ and GZIP sources in your browser without uploading their contents to a conversion server.

Browser-first archive conversion with fail-closed safety

The live Archive converter handles ZIP, TAR, TAR.GZ/TGZ, GZIP/GZ, 7Z, and supported RAR4/RAR5 inputs locally. 7Z and RAR are decoded only when needed through the lazy WASM path; certified public outputs remain ZIP, TAR, and TAR.GZ.

Fail-closed archive policy

Source files are signature-checked before admission. During parsing and before output, the engine rejects corrupt containers, unsafe or duplicate normalized paths, unsupported links and special entries, and archives that exceed entry-count, per-entry, expanded-size, path-size, or browser-memory safety limits.

What the production Archive engine protects

No silent TAR loss: hard links, symbolic links, device entries, FIFOs and unknown special entry types are rejected instead of disappearing from the converted archive.
No ambiguous overwrite: duplicate normalized paths are rejected before ZIP/TAR/TAR.GZ output is generated.
Path hygiene: parent traversal, absolute roots, Windows drive roots, control characters and excessively long paths are rejected.
Clear failure classes: password/unsupported-feature errors are permanent, corruption/incomplete containers are permanent, and only transient decoder-runtime failures remain retryable.
WASM defense in depth: the 7Z/RAR decoder independently enforces the current 75 MB source policy before copying the source into WASM memory.
Fidelity coverage: Unicode names, zero-byte regular files, nested paths, empty directories, timestamps, and compatible basic permissions are covered by the Archive regression surface.

Lazy WASM, not server conversion

The 7Z/RAR compatibility layer is pinned to a fixed libarchive-wasm build. Its JavaScript, WASM binary, and wrapper license are verified by Git blob hash during the site build and served as same-origin static assets. Normal ZIP, TAR, and GZIP users do not initialize this runtime.

Compatibility boundary

The converter does not promise exact preservation of symbolic links, hard links, ownership IDs, ACLs, extended attributes, sparse files, or vendor-specific metadata. Rather than silently omitting unsupported entries, it rejects archives whose meaning cannot be safely represented by the certified output path.

7Z and RAR remain input-only. ConvertAnyFile does not advertise 7Z or RAR output until a writer path has its own compatibility, fidelity, and browser test matrix.

For practical walkthroughs, see the RAR to ZIP guide, 7Z to ZIP guide, and TAR.GZ to ZIP guide.

FAQ

Archive converter FAQ

Practical details for local 7Z, RAR, ZIP, TAR, TAR.GZ, and GZIP conversion.

Are my archive contents uploaded?

No. Supported 7Z, RAR, ZIP, TAR, TAR.GZ/TGZ and GZIP conversion runs in a browser worker on your device. The source archive is not sent to a conversion server.

Which archive formats are supported?

ZIP, TAR, TAR.GZ/TGZ, GZIP/GZ, 7Z, and supported RAR4/RAR5 are accepted as inputs. 7Z and RAR use a lazy-loaded WASM decoder. Certified public outputs are ZIP, TAR, and TAR.GZ.

How are corrupt or ambiguous archives handled?

The converter fails closed. Corrupt or incomplete containers, unsafe or duplicate normalized paths, password-protected archives, links, unsupported special entries, and archives over browser safety limits are rejected instead of producing partial output.

What happens if the 7Z/RAR decoder cannot load?

A decoder-runtime load failure is treated as temporary and can be retried. Permanent input problems such as corruption, encryption, unsupported archive features, or safety-policy violations are not presented as retryable.

Does converting an archive change the files inside it?

Regular file payload bytes are repackaged rather than intentionally transformed. Archive-specific metadata that has no safe equivalent in the target format may not be preserved, and unsupported special entries are rejected.