Create TAR
Bundle files and whole folders into a TAR archive, optionally GZIP-compressed (.tar.gz), the standard format for Linux, servers and source releases. Folder structure, file times and long or non-English names are preserved.
Create TAR
Add files and folders and download a .tar or .tar.gz archive.
Drop files or folders here
Folders keep their structure inside the TAR
Files stay on your device. Nothing is uploaded.
How to use Create TAR
- 1
Add files and folders
Drag and drop files or whole folders, or use the file picker. Folder selection is available in browsers that support it.
- 2
Choose the format
Pick plain
.tar, or.tar.gzwith a GZIP level: fast, balanced or maximum. - 3
Build the archive
The TAR is written in your browser, with folder structure, file times and long or non-English names kept.
- 4
Download
Save the
.taror.tar.gz. Nothing is uploaded.
Why use Aback ZIP's Create TAR?
The Unix standard
TAR and .tar.gz are what Linux servers, source releases and many deployment tools expect, and tar on Linux, macOS and Windows 10 or later opens them.
Folders kept as they are
Every folder gets its own entry, empty folders included, and each file keeps its modification time.
Long and non-English names
Paths longer than 100 characters and names in any language are stored with standard pax headers, which GNU tar, BSD tar and 7-Zip read.
Built on your device
The archive is assembled in your browser. Files are not uploaded, and no account is needed.
Common use cases
Uploading a site to a server
Pack a website or app into one .tar.gz, upload it, and unpack it on the server with tar -xzf.
Source releases
Publish a .tar.gz of your project next to the ZIP, the format Linux users and package builders usually look for first.
Tools that require TAR
Some upload forms, deployment tools and hosting panels only accept .tar or .tar.gz. Make one without a terminal.
From Windows to Linux colleagues
Send a folder from Windows to someone on Linux in the format their tools handle by default.
Datasets and exports
Bundle a folder of CSV or JSON files into a .tar.gz for a data pipeline or a research repository that expects it.
Keep empty folders
Folder structures where empty directories matter, such as project templates, are stored with every folder intact.
About Create TAR
TAR or TAR.GZ?
| .tar | .tar.gz | |
|---|---|---|
| Compression | None; files are stored one after another | The whole TAR is compressed with GZIP |
| Size | The same as the files combined, plus small headers | Usually much smaller for text, code and data |
| Best for | Files that are already compressed, or a tool that wants plain TAR | Most other uses, especially sending or uploading |
GZIP compresses the whole TAR as one stream, so repetition across files helps. Photos, video and archives don't shrink much either way. The fast level saves time on large files; maximum gives a slightly smaller file for one you will share many times.
Permissions, owners and names
Browsers don't expose Unix permissions or file owners, so every file is stored with mode 644 (owner can write, everyone can read) and every folder with 755. No user or group names from your computer are stored. If a script must be executable after extraction, run chmod +x on it afterwards.
Names longer than the classic 100-character limit and names with non-ASCII characters are stored using pax extended headers, the POSIX standard for this. If two items would get the same path, the second is renamed with " (1)" so nothing is overwritten.
What is kept and what changes
| Item | Result | Notes |
|---|---|---|
| File contents | Preserved | Stored byte for byte; .tar.gz adds lossless GZIP compression. |
| Folder structure | Preserved | Every folder gets an entry, including empty ones. |
| File modification times | Preserved | As reported by your browser. |
| Long and non-English names | Preserved | Stored with pax headers. |
| Duplicate paths | Changed | Renamed with " (1)" instead of overwriting each other. |
| Unix permissions and owners | Changed | Set to 644 for files and 755 for folders, with no owner names, because browsers don't expose them. |
Limitations
- Output is
.taror.tar.gzonly..tar.xz,.tar.bz2and.tar.zstcan be opened with Extract TAR but not created. - Unix permissions are not carried over: files get mode 644 and folders 755. Executable scripts need
chmod +xafter extraction. - The archive is built in browser memory. There is no fixed size limit, but multi-gigabyte archives may fail on phones and low-memory devices.
- Folder selection isn't available in every browser. Where it isn't, add the files individually.
Processing happens locally in your browser. Your files are not uploaded, and closing the tab discards everything.
Related tools
Create TAR: frequently asked questions
No. The archive is built in your browser and saved straight to your device. Nothing is sent to a server and no account is needed.
Add your files and folders, choose .tar.gz and a GZIP level, and download. On Linux, macOS or Windows 10 and later, tar -xzf archive.tar.gz unpacks it.
TAR and .tar.gz suit Linux servers, source releases and tools that expect them. For sending files to people on Windows or macOS, a ZIP from Create ZIP opens with a double-click everywhere.
No. Browsers don't let websites read Unix permissions or owners, so files are stored with mode 644 and folders with 755. Set execute permissions with chmod +x after extracting if you need them.
Yes. Every folder is stored as its own entry, so empty folders are recreated when the archive is extracted.
No. Those formats can be opened with Extract TAR and XZ, BZ2 & ZST Extractor, but only .tar and .tar.gz can be created here.
Yes. Names in any language, and paths longer than 100 characters, are stored with standard pax headers that GNU tar, BSD tar and 7-Zip understand.