katlab tools/extract/jar support on Ko-fi

Extract .jar Files Online

Open a Java .jar, .war or .ear, read its manifest and resources, and open the JARs nested inside it without unpacking everything first.

Files are processed locally. Nothing is uploaded to a server.
JARWAREARnested archivesno JDK needed

How to extract a JAR file without the JDK

  1. Drop the .jar, .war or .ear onto the box above, or click to choose it.
  2. Browse the package tree or search for a class or resource name. Click META-INF/MANIFEST.MF or a properties file to read it.
  3. Download what you need, or use the open icon on a nested JAR to step into it.

Java archives are ZIP files with conventions

A JAR is a ZIP archive with a META-INF folder and a manifest. A WAR is the same idea for a web application, with WEB-INF/classes and WEB-INF/lib. An EAR wraps several modules for an application server. Double-clicking one either tries to run it or does nothing, and the jar command needs a JDK that is often missing on the machine where the question comes up.

Here the archive opens as a folder tree. Text resources such as the manifest, .properties, XML descriptors, YAML, SQL scripts and templates open in the preview with syntax highlighting.

Archives inside archives

Real deployments are nested: a WAR carries its dependencies as JARs under WEB-INF/lib, an EAR carries WARs and JARs, and executable application JARs often bundle every library inside themselves. Each nested archive has an open icon. Click it and you are inside that JAR, with a breadcrumb to get back out.

That makes the usual support questions quick to answer: which version of a library was shipped, whether a config file made it into the build, what the manifest’s Main-Class or Class-Path says.

What it does not do

.class files are compiled bytecode. They are listed and can be downloaded or viewed as hex, but they are not decompiled to Java source. The tool also does not run the archive or verify its signature. Build artefacts are read on your device and are not uploaded, so proprietary code stays where it is.

Frequently asked questions

Can I open a JAR file without Java installed?

Yes. The archive is read in the browser. No JDK or JRE is needed to browse it and extract files.

Does it decompile .class files?

No. Class files are extracted as they are. To read them as source you need a separate Java decompiler.

Can I look inside the JARs in WEB-INF/lib?

Yes. Nested archives can be opened in place from the file list, so you can step from a WAR into one of its library JARs and back.

How do I find which JAR contains a class?

Search covers the whole archive you have open. Open the JAR, type the class name, and the matching entries are listed with their package path. For a WAR or EAR, open the nested JAR you want to search.

Is my JAR uploaded to a server?

No. The file is processed locally in your browser and the page works offline once loaded.