Forge and Fabric can work with PojavLauncher, but version matching matters more on a phone where memory and graphics headroom are limited. Match the Minecraft version, loader and mod build first; then add mods gradually so a bad jar is easy to identify.
Key points
- Install the mod loader first, launch it once with no mods, then add jars a few at a time.
- Game version, loader type and mod version must all match exactly — mobile is unforgiving about this.
- Fabric is the better starting point on phones; Forge suits larger packs but needs more memory.
- Fabric API is a dependency for most Fabric mods and its absence causes silent load failures.
How mod loaders work here
A mod loader is a modified game entry point. It loads before Minecraft, reads your mods folder and injects each mod into the running game. PojavLauncher does not replace that system — it simply runs it, exactly as a desktop launcher would.
Forge
The older and broader ecosystem. Large content packs, machinery mods and long-running community projects tend to be Forge first. It carries more overhead, which matters on a phone.
Fabric
Lighter and faster to update. Performance mods and quality-of-life additions usually appear here first. On mobile hardware Fabric is generally the better starting point.
They do not mix
A Forge mod will not load under Fabric and the reverse is equally true. Mixing them in one mods folder is the most common cause of an instant crash on launch.
Installing a loader
The loader has to be installed into the launcher before any mod will be recognised. The process differs slightly between the two but follows the same shape.
Installing Fabric
Download the Fabric installer jar for your target game version, then use the launcher's install-jar option to run it. A new profile appears in the version list once it completes. Add the Fabric API jar to your mods folder — most Fabric mods require it and will fail silently without it.
Installing Forge
Download the Forge installer for the exact game version and run it the same way. Forge installs take noticeably longer and need more free storage. Wait for the process to finish rather than switching apps.
Verifying the profile
After installation, select the new profile and launch once with no mods installed. If vanilla-with-loader starts cleanly, the loader is fine and any later crash is a mod problem.
Adding mods correctly
Mods are jar files that live in a specific folder. Getting them into the right place is trivial; getting the versions right is where people lose an evening.
Finding the mods folder
The launcher exposes a file manager. Navigate to the .minecraft directory and open the mods folder, creating it if the loader has not already. Copy jars in directly — do not unzip them.
Matching versions exactly
A mod built for 1.20.1 will not run on 1.20.4. Loader version, game version and mod version all have to line up. Download pages state all three; read them before downloading.
- Game version must match the mod's stated version
- Loader must match the mod's loader type
- Dependencies such as Fabric API must be present
- Library mods usually need installing before the mods that use them
Start with three mods, not thirty
Add a small set, launch, confirm it works, then add more. Debugging one new mod is quick. Debugging a folder of forty at once is not.
Memory and performance with mods
Every mod costs memory, and mobile devices have far less headroom than a desktop. This is the practical ceiling on mobile mod packs.
Allocating sensibly
Around 2 GB suits a light Fabric set-up. Larger Forge packs want 3 GB or more, which realistically means an eight gigabyte device. Allocating beyond half your total RAM invites the system to kill the process mid-game.
Performance mods worth adding first
Rendering optimisation mods often pay for themselves several times over, recovering more frames than they cost. Add them before any content mod so you have headroom to spend.
When a modded launch fails
Crash logs look intimidating but are usually readable. The failing mod is normally named within the first few lines of the exception.
Reading the log
Look for a line naming a mod id or jar filename close to the exception. Remove that mod, relaunch, and confirm.
Bisecting the mods folder
If the log is unclear, move half the mods out and relaunch. Repeat on whichever half fails. Five minutes of this beats an hour of guessing.
Known mobile limitations
Some shader packs and mods that rely on advanced desktop OpenGL features simply will not run through the renderer bridge. That is a hardware and translation limit, not something a setting will fix. The error guide lists the ones that come up most.
Building a mod pack that stays stable
Stability on mobile comes from restraint rather than clever configuration. A small, deliberate set of mods will outperform a large one on the same device every time.
Add performance mods first
Install rendering and memory optimisation mods before any content mod. They free up headroom that the content mods then spend, and testing them on their own tells you what the device can handle.
Keep a working snapshot
When a set of mods runs cleanly, copy the mods folder somewhere safe. Restoring a known-good folder takes seconds and saves rebuilding a pack from memory after an experiment goes wrong.
Match server and client packs exactly
Joining a modded server requires the same mods at the same versions on your device. Mismatches are rejected at connection time with an error listing the offending mod, which is at least a clear message to work from.
Download reminder: take the build from the project's own repository. The download section on our homepage links straight to it.