Skip to content

Free online CLASS to JAR converter

Package Java bytecode and resources into a Java ME JAR with valid MIDlet metadata.

Convert CLASS to JAR online - free

Uploading…

Your file is processed automatically and deleted right after you download the result, or after 3 hours at the latest.

How it works

  1. 1/3

    Upload your .class file

    Click to browse to select your file you want to convert or simply drag & drop your file into selected area.

  2. 2/3

    Perform .class to .jar conversion

    After successful file upload, click to convert when you are ready.

  3. 3/3

    Download converted .jar file

    Conversion result is ready to download.

How to convert class to jar file

A Java ME phone, emulator, or deployment tool may require a single .jar instead of separate Java .class files. Packaging combines the compiled classes and resources without changing their bytecode.

What the .class format is

A .class file contains Java Virtual Machine bytecode compiled from Java source, normally with javac. Java ME applications, mobile games, libraries, and emulators commonly use multiple class files arranged in package directories such as com/example/App.class.

One class file normally represents one compiled type, not a complete application. The type may require other classes, images, configuration files, or Java ME APIs supplied by the phone or emulator. Developers, Java ME toolchains, emulator projects, and users handling legacy mobile applications encounter this format.

What the .jar format is

A JAR is a ZIP-based Java archive containing class files, resources, and optional metadata. It preserves the compiled bytecode and package paths; it does not compile, decompile, optimize, or translate the classes.

For Java ME, the JAR commonly contains a MIDlet and is distributed with a separate Java Application Descriptor using the .jad extension. A JAR is not inherently an installable application: Java SE launchers may use a manifest Main-Class, while Java ME devices use MIDlet metadata and the required Java ME profile.

Package the files with the JDK

  1. Install a Java Development Kit. Its jar command is more suitable than a generic online converter because it preserves paths and does not upload proprietary classes.
  2. Create a staging directory with the original package hierarchy. For example, use build/com/example/App.class, not a renamed App.class at the archive root. Copy required images, data files, and other resources into the corresponding locations under build.
  3. From the directory containing build, run jar cf app.jar -C build .. On JDK versions supporting long options, jar --create --file app.jar -C build . is equivalent.
  4. Inspect the result with jar tf app.jar. Check that every class has its declared package path and that resources required at runtime are present.

For a standard Java application, add a manifest containing Manifest-Version: 1.0 and Main-Class: com.example.App, ending with a blank line, then run jar cfm app.jar MANIFEST.MF -C build .. This Main-Class entry does not replace Java ME MIDlet metadata.

Build a Java ME MIDlet JAR

A Java ME MIDlet manifest normally declares entries such as MIDlet-Name, MIDlet-Version, MIDlet-Vendor, MIDlet-1: App,,com.example.App, MicroEdition-Configuration: CLDC-1.1, and MicroEdition-Profile: MIDP-2.0. The exact configuration and profile must match the target device.

Create the accompanying app.jad with the required matching metadata, including MIDlet-Jar-URL: app.jar and MIDlet-Jar-Size. The size must be the exact number of bytes in the final JAR, so generate or update the JAD after packaging. Java ME SDK tools, the Java ME NetBeans toolchain, and device-specific deployment tools can generate, preverify, and validate these files; the JDK jar command only creates the archive.

Online and desktop options

Desktop packaging with the JDK, Apache Ant, Maven, or a Java ME SDK is the appropriate choice when manifests, preverification, dependencies, or reproducible builds matter. IDEs such as NetBeans with Java ME support can compile the source, assemble the JAR, generate the JAD, and run device or emulator checks.

No reputable online converter can turn arbitrary class files into a valid Java ME application by conversion alone. A generic ZIP service may package files and let you rename the result to .jar, but it cannot determine dependencies, correct package paths, perform CLDC preverification, or create valid device metadata. Use an online archive service only for non-sensitive files when you need simple ZIP-style packaging and will validate the result locally.

Compatibility limitations

The target must support the bytecode level, Java ME configuration, profile, APIs, libraries, and device limits used by the classes. Packaging incomplete or incompatible files does not fix missing dependencies, verification failures, unsupported APIs, incorrect manifests, or insufficient memory.

CLDC devices commonly require preverified class files; use the target Java ME SDK or its preverification tool before deployment when required. Keep the archive paths and case exactly as expected by the classes and resources.

Android applications are not installed as ordinary Java ME JARs. Android uses DEX bytecode inside APK or app-bundle packages, although a JAR may serve as a Java library during an Android build.

CLASS vs JAR: format comparison

How the CLASS and JAR formats compare on the properties that matter most for this conversion.

Comparison of the CLASS and JAR file formats
Property .CLASS Java bytecode class file .JAR Java Archive
Open standard Partly open Yes
Compression Uncompressed Both
Typical file size Small Medium
Opens in a web browser No No
Further editing Limited Limited
Metadata support Basic Basic
Plain-text readable No No
Best used for Professional production Embedding in applications
Introduced 1995 1996
Developer Sun Microsystems (now Oracle) Oracle (originally Sun Microsystems)
MIME type application/java-vm application/java-archive

Information about file extensions and file types is provided by File-Extensions.org

The database currently does not contain any direct class file converter links.

Frequently asked questions

Is the CLASS to JAR converter free?

Yes, converting CLASS to JAR on 101convert.com is completely free. No registration, email address or installation is required. If you need a higher file size limit or want to convert more files at once, see our plans.

How large can my CLASS file be?

You can upload CLASS files up to 30 MB and convert up to 3 files at once in a single batch. With a paid plan the limit is up to 200 MB per file and 5 files at once, see our plans.

What happens to my uploaded files?

Files are processed automatically. Your upload is deleted from our servers right after you download the result, or after 3 hours at the latest. We never view or share your files.

Do I need to install any software to convert CLASS to JAR?

No. The CLASS to JAR conversion runs entirely online in your browser and works on Windows, Mac, Linux, Android and iPhone.

Did the conversion fail?

In most cases, the cause is an incorrect file format. Please upload a valid CLASS file for this CLASS to JAR conversion. Occasionally, the issue may be on our side. We analyze recurring conversion failures and disable or fix the converter if we detect a defect.

Additional formats for
class file conversion

Convert to jar from
other formats

Share on social media:

Already downloaded

This file has already been downloaded. For your privacy it was deleted from our server right after the download, so it cannot be downloaded again. To get it once more, convert the file again.