FastQuit in one minute
FastQuit changes the moment you leave an integrated single-player world. Instead of keeping you on Minecraft's saving screen for the entire save, it can return you to the title screen while the world continues saving in the background. The selected release on this page is FastQuit 3.1.5+mc26.2 for Minecraft Java Edition 26.2 on Fabric.
The distinction matters: FastQuit shortens the wait before you can use the title screen; it does not promise that your storage device writes world data faster. The upstream project also makes some operations wait when they need the same world or storage session. Quitting the whole game still waits for the background save. That is the safety behavior you want—never kill the process just because the menu appeared quickly.
fastquit-3.1.5+mc26.2.jarVersion ID:
ZZ5dfboCEnvironment: client only
License: MIT
Download and compatibility table
| Component | Use this selection | Required? |
|---|---|---|
| Minecraft | Java Edition 26.2 | Yes |
| Loader | Fabric Loader 0.16.9 or newer; use the current installer build for 26.2 | Yes |
| FastQuit | 3.1.5+mc26.2 — fastquit-3.1.5+mc26.2.jar |
Yes |
| Fabric API | 0.158.0+26.2 was the latest checked stable 26.2 Fabric release on August 27, 2026 | Yes |
| Cloth Config API | 26.2.155+fabric was the current checked 26.2 Fabric release | Yes |
| Java | 25 or newer, as declared by the selected FastQuit JAR | Yes |
| Mod Menu | Matching 26.2 Fabric build | Optional; provides an in-game config button |
Do not mix the Minecraft 26.2 file with a 1.21.x or 26.1 instance. Do not load this Fabric JAR with NeoForge. The selected JAR declares a client environment and the official project marks dedicated-server support as unsupported, so install it in each player's local client profile—not in the server's mods directory.
Download FastQuit 3.1.5 for Minecraft 26.2
Required local dependencies: Fabric API for Minecraft 26.2 and Cloth Config API for Minecraft 26.2. Install them beside FastQuit in the same mods folder.
Install FastQuit safely
- Back up the world you will use for the first test. A copied
saves/<world>folder is enough for a local safety copy when Minecraft is fully closed. - Create or select a Minecraft 26.2 Fabric profile. Launch it once, then close the game.
- Confirm that the profile uses Java 25 or newer.
- Place the FastQuit JAR, the matching Fabric API JAR, and the matching Cloth Config JAR in that profile's
modsfolder. Add Mod Menu only if you want an in-game configuration screen. - Remove older FastQuit copies. One profile should contain exactly one FastQuit JAR.
- Start the game, open a disposable or backed-up single-player world, move around long enough to load a few chunks, and choose Save and Quit to Title.
- Keep the game open until FastQuit reports that saving is complete. Then re-enter the world and confirm that your player position and recent block changes were saved.
Nothing needs to be installed on a remote multiplayer server. FastQuit acts on Minecraft's integrated single-player server; it does not accelerate your network connection or a server operator's save cycle.
What you can do while the world is saving
The title screen may become available before the save finishes, but operations that need the same world can still be delayed. The upstream documentation says rejoining a saving world waits, creating a backup of that world waits, and quitting the game waits for completion. Treat that wait as a guardrail. If an edit, delete, optimize, upload, or recreate action appears to pause, let it finish instead of force-closing Minecraft.
A good first-session rule is simple: leave saving notifications visible and do not shut down the Java process until completion is reported. Returning to the menu is not the same event as all world data reaching disk.
Settings explained
With Mod Menu installed, open Mods → FastQuit → Configure. Without Mod Menu, close Minecraft before editing .minecraft/config/fastquit-config.txt (or the equivalent config path inside your launcher profile).
- Show Toasts controls FastQuit's save-status notifications. Keep it enabled until you understand the workflow.
- Background Thread Priority accepts values from 0 through 10. Upstream documents 0 as disabling its priority adjustment. Start with the default; increasing priority can compete with the title screen or another world for CPU time.
- Render Saving World Screen controls whether the familiar saving-world view remains part of the transition.
- Show Saving Time uses three documented values: 0 disables the time display, 1 shows it on the completion toast, and 2 also shows it on the world list.
- Allow Multiple Servers can let another integrated world start while an earlier one finishes. The selected source automatically disables this behavior around several known conflicting mod IDs. Leave the default unchanged unless you have a backed-up test case and understand the compatibility tradeoff.
Change one setting at a time. Use the same test world and the same route before comparing results; otherwise chunk count, active entities, datapacks, storage load, and other mods can swamp the difference.
How to measure the result honestly
Record two separate timings: (1) the time from clicking Save and Quit to Title until the title screen is usable, and (2) the time until the save-complete notification appears. FastQuit is designed primarily around the first measurement. Run three passes after similar play in the same backed-up world, and report the median rather than the fastest result.
Also record your loader, FastQuit version, dependency versions, Java version, drive type, and mod list. A large modpack on a busy hard drive is not comparable to a light profile on an SSD. Do not advertise a universal percentage or a guaranteed number of seconds.
Compatibility notes
The upstream page specifically describes compatibility handling for Fast Backups 0.17 or newer and Wakes 0.4.0 or newer. That is not a guarantee for every future combination. If you use a backup, world-management, integrated-server, or shutdown-related mod, test the pair in a copied world before trusting your main save.
When investigating a problem, keep Fabric API and Cloth Config installed and temporarily remove only unrelated mods. A successful clean-profile test usually points to a mod interaction; a failure in the clean profile usually points to a wrong game/loader/Java tuple or a problem worth reporting upstream.
Troubleshooting
FastQuit says a dependency is missing
Install Fabric API and Cloth Config API for Minecraft 26.2 and Fabric. Fabric API is not the same thing as Fabric Loader; FastQuit needs the relevant API module supplied by the full Fabric API package. Do not substitute Forge or NeoForge builds.
The game crashes before the main menu
Check that you are running Minecraft 26.2, Fabric, Java 25+, and only one FastQuit JAR. Read the first dependency or version error in logs/latest.log. If the log names another mod, reproduce in a clean 26.2 Fabric instance containing only FastQuit, Fabric API, and Cloth Config before filing an issue.
I returned to the title screen, but saving still takes a while
That can be expected. The mod changes when you regain the menu; it does not guarantee shorter disk-write time. Let the background task finish. Large newly generated areas, entity-heavy worlds, slow storage, backups, and competing processes can extend the second timing.
Rejoining, backing up, or closing the game pauses
Those operations may need to wait for the current save. Do not end the Java process. Leave notifications on, wait for completion, and then retry. A pause that never resolves should be reproduced in a copied clean-profile world with the log retained.
There is no Configure button
Mod Menu is optional. Install its matching 26.2 Fabric build for an in-game button, or close Minecraft and edit FastQuit's config file directly. Cloth Config remains required even if Mod Menu is absent.
The mod does nothing on a multiplayer server
FastQuit is a client-side integrated-server workflow mod, not a dedicated-server performance mod. Leaving a remote server does not invoke the same single-player world-saving path.
Update or remove FastQuit
Before updating, let every background save finish, close Minecraft completely, and back up important worlds. Replace the old FastQuit JAR rather than keeping two versions. Recheck the new file's Minecraft version, loader, Java requirement, and dependencies. Your config may remain, so review it if upstream adds or changes options.
To remove FastQuit, finish the current save, close the game, delete only the FastQuit JAR, and leave Fabric API or Cloth Config if another installed mod needs them. The world format is not advertised here as being changed by FastQuit, but a normal backup remains the safest removal practice.
File verification, license, and source
The local download is the official Modrinth release file fastquit-3.1.5+mc26.2.jar. MineBrush also keeps the matching source snapshot and MIT license attached to this article for transparency.
FastQuit is distributed under the MIT License. MineBrush must keep the upstream copyright and permission notice with any mirrored copy; the package includes that exact text. The corresponding transparency source is pinned to upstream commit 8efed17360a89ca0b23d56a88830a2b3d535eeed, whose message is “Version 3.1.5” and whose build properties declare Minecraft 26.2 and mod version 3.1.5. Fabric API and Cloth Config are separate projects with separate licenses and are not silently bundled into the FastQuit JAR.
FastQuit FAQ
Does FastQuit save my world instantly?
No. It can return you to the title screen while saving continues. The total save can still take time.
Can I close Minecraft as soon as the menu appears?
No. Let the background save complete. The upstream behavior makes a normal game quit wait; force-closing the process defeats that protection.
Is FastQuit required on a server?
No. The selected build is client-only and the official project marks dedicated servers unsupported.
Does it work with NeoForge?
Not this file. fastquit-3.1.5+mc26.2.jar is a Fabric build.
Which dependencies are required?
Fabric Loader, Fabric API, and Cloth Config API for Minecraft 26.2. Mod Menu is optional.
Where is the config file?
Use Mod Menu's Configure button, or edit config/fastquit-config.txt in the active launcher instance while Minecraft is closed.
Can I install FastQuit in an existing world?
Test in a backup first. Use the exact version tuple and verify a completed save plus a successful rejoin before relying on it in your main world.
Where should I report a reproducible bug?
Use the upstream FastQuit GitHub issue tracker. Include the full game version, Fabric Loader, Java, FastQuit and dependency versions, the smallest reproducible mod list, and the relevant log.
Official and creator sources
- FastQuit: 3.1.5+mc26.2 · Fabric · Release
- Fabric API: 0.158.0+26.2 · Fabric · Release
- Cloth Config: 26.2.155+fabric · Fabric · Release
- FastQuit source: 3.1.5 commit boundary · Fabric
These links identify the official or creator-controlled evidence checked on August 28, 2026. MineBrush has not treated an unverified runtime result, device outcome, or third-party configuration as guaranteed.

PLAYER QUESTIONS
Discussion
Include the exact edition, version and step when asking for help.