About JAR Files
Java Archive
JAR is a ZIP-based archive for Java class files, metadata, and resources.
Family
Archives & Compressed
Extension
.jar
MIME Type
application/java-archive
Can Use As
HOW JAR
CAME TO BE.
JAR — Java ARchive — shipped with Java 1.1 in 1997 as the standard packaging format for Java applications and applets. A JAR is a ZIP file with specific conventions: the META-INF/MANIFEST.MF declares the main class, supporting libraries go in the archive root, and optional cryptographic signatures live in META-INF too. Sun’s goal: one file to download, one JVM to execute it.
For 25 years JAR was the universal Java distribution format. Applets in browsers, enterprise apps on Java EE servers, Minecraft mods, Android bytecode before DEX conversion — all JAR. Modern Java (9+) introduced JMOD for modular applications, but JAR remains the dominant format. Every major IDE’s output, every Maven/Gradle artifact, every Spring Boot fat-JAR (which bundles the whole app and its dependencies into one executable JAR) is still a JAR file.
CURIOSITIES &
TRIVIA.
A JAR is a ZIP archive with a mandatory META-INF/MANIFEST.MF declaring what class to run with `java -jar file.jar`.
Minecraft Java Edition's core game, every mod, and every modpack launcher ship as JAR files — hundreds of millions of downloads.
Spring Boot "fat JARs" bundle the entire application plus its dependencies and an embedded Tomcat — single-file web services.
Before Android, JAR files ran as-is on Java ME phones — the precursor to today's app stores.
The Java applet era (1996-2015) made JAR files in browsers a common sight before browser vendors killed NPAPI plugins.
STRENGTHS &
LIMITATIONS.
Strengths
- Universal Java distribution since 1997.
- Self-contained: one file holds code, resources, and signatures.
- Executable via `java -jar` with zero setup beyond a JVM.
- Cryptographic signing for code provenance.
- Nested JARs supported (common in Spring Boot).
Limitations
- Requires a JVM to run.
- Java applet era left a security-scare legacy; browsers no longer execute JARs.
- Native code distribution (JNI) complicates cross-platform JARs.
- Modular Java (JPMS, 2017) introduced JMOD as a partial successor.
Typical Sizes & Weights
Small utility library
50-500 KB
Spring Boot fat JAR
15-80 MB
Minecraft client
~5 MB (plus assets)
Technical Specifications
- MIME type
- application/java-archive
- Extension
- .jar
- Container
- ZIP with META-INF/MANIFEST.MF
- Variants
- .war (web), .ear (enterprise), .jmod (modular)
- Compression
- Deflate (ZIP default)
CONVERT FROM
JAR
Common Use Cases
Java applications, libraries
Related Formats
Popular comparisons
JAR vs 7Z
Differences, file size, and when to choose each format.
JAR vs TAR
Differences, file size, and when to choose each format.
JAR vs GZ
Differences, file size, and when to choose each format.
JAR vs BZ2
Differences, file size, and when to choose each format.
JAR vs XZ
Differences, file size, and when to choose each format.
JAR vs LZMA
Differences, file size, and when to choose each format.
Popular JAR conversions
The most-requested destinations when starting from JAR.
Frequently Asked Questions about JAR
Frequently Asked Questions
JAR (Java Archive) is an archive format used to bundle multiple files and folders into a single compressed file. The archive preserves the directory structure and typically reduces total size via compression. JAR sits in the archives & compressed family and has specific strengths around compression ratio, speed, or platform support.
7-Zip, WinRAR, The Unarchiver (macOS), and the built-in archive utilities on Windows and macOS open most JAR files. For command-line extraction, 7z, unar, or the format-specific tool handles JAR cleanly. If your extractor does not recognise JAR, convert to ZIP first — ZIP opens on every operating system without extra software.
Upload the JAR to KaijuConverter and pick ZIP, 7Z, TAR.GZ, or RAR as the target. Our pipeline extracts the original archive and re-compresses the contents into the target format. File permissions, timestamps, and directory structure are preserved where both formats support them.
Depends on the goal. ZIP is the universal baseline — every OS extracts it out of the box. Formats like 7Z or TAR.GZ compress better but require specific tools. JAR may win on compression ratio, password support, or OS integration for specific workflows; ZIP wins on raw compatibility.