GZIP Compressor

Shrink a large CSV or JSON export before emailing it or uploading it to a data tool that accepts .gz, compress database dumps (.sql) before storing or transferring them, prepare pre-compressed web assets such as app.js.gz for a server or CDN that serves them directly, archive old log files the way servers do, and reduce the size of text-based backups. Because gzip is supported natively by servers, databases and data tools, a .gz file can usually be used without unpacking it first. Gzip is also fast: compressing even large text files takes only a moment, and unpacking is faster still. For files you share with Windows users who don't have an archive tool, a ZIP may be friendlier, since ZIP opens in Windows Explorer without extra software.

Gzip finds and replaces repeated patterns, so text-based files shrink the most. Files that are already compressed hardly change, and can even grow slightly.

A .gz file holds exactly one file; gzip has no folders and no list of contents. That is why each file you add becomes its own .gz. To put several files or a folder into one compressed archive, use the TAR Creator to make a .tar.gz, the format Linux uses for exactly that, or the ZIP Creator for a ZIP that opens on any computer.

Every Linux and macOS system can unpack .gz files with gunzip, and tools such as 7-Zip and WinRAR open them on Windows. Many programs read gzipped data directly — databases import .sql.gz dumps, data tools read .csv.gz, and browsers decode gzipped web pages automatically. To unpack a .gz in your browser, use the GZIP Decompressor.

Compression uses the CompressionStream feature built into modern browsers, which streams through large files without loading them fully into memory. Nothing is sent to a server, so logs, customer data and backups stay on your device. The original file name is kept in the .gz file name rather than inside the file, as browsers' gzip encoder does not store it.