Guide
JAR and JAD Files, Explained Simply
What a JAR file is, what a JAD file adds, why Java games arrive as one or both, and what J2ME Loader does with each.

CONTENTS On this page
The JAR is the game
A JAR file is the game itself: a packed archive holding the program code, the pictures, the sounds and the levels, everything a Java phone needed in one small parcel. When people say they kept their Java games, they mean a folder of these. The loader from J2ME APK home exists to open exactly this format.
Sizes tell the era story. Most JARs are a few hundred kilobytes; the epics reach a few megabytes. Your whole childhood gaming shelf can weigh less than one photo from a modern phone camera.
The JAD is the label
A JAD is a tiny text file that describes the JAR: its name, its maker, its size, where the JAR lives. Old phones and stores used it to check a game before committing to the full download, the way a label is read before a jar is opened, an analogy the format names almost beg for.
Some games install happily from the JAR alone. Others were distributed expecting their JAD beside them. Keeping the pair together in one folder is the zero effort habit that prevents every JAD mystery, as our adding games guide recommends.
What the loader does with them
Point the loader at the JAR and it reads the game manifest inside, installs the title into your library, and builds its profile. A JAD in the same folder is read for its details when the game expects it. From then on, neither file is needed at launch time in your hands; the library entry is the game, as far as your thumbs are concerned.
Keep your originals anyway. They are your backup, your collection in its purest form, and the same files that would run on a PC setup or an original handset.
File detective work
A file named .jar that will not install is usually one of three things: a cut short download, a desktop Java program wearing the same extension, or a renamed archive that was never a phone game. The cure is a clean copy of a real Java ME title, after which the loading fixes rarely need opening.
Two files, one game, no mystery. That is the whole format, and it has carried a generation of games safely into the present.
Here is a small test of understanding to close: a friend hands you a single small file and a tiny text file and says the game does not work. You now know to ask three questions. Is the big file complete? Is it truly a phone game? Is its little label beside it in the folder? Most mysteries die at one of those gates. That is the real gift of understanding formats: not trivia, but the calm of knowing where problems live. J2ME Loader handles the rest automatically, and honestly, after this page, so do you. The JAR is the game, the JAD is its label, and J2ME Loader is the shelf they live on.
Quick Answers
Do I need both JAR and JAD to play?
Usually the JAR alone is enough. When a JAD exists for a game, keep it beside the JAR, since some titles expect the pair.
What is inside a JAR file?
Everything the game needs: code, graphics, sound and data, packed into one small archive.
Why is my JAR so small compared to modern games?
Java games were built for phones with tiny storage and slow processors. A few hundred kilobytes was a normal, complete game.