Screenshot 1 of 1. MinecraftHub-generated editorial cover for FastQuit, a voxel diorama around the lime MinecraftHub block
What FastQuit works with.
| Platform | Java Edition |
|---|---|
| Loaders | Fabric |
| Minecraft versions | 1.17, 1.17.1, 1.18.2, 1.19.4, 1.20.6, 1.21.11, 26.1.2, 26.2, 26.3 |
| Environment | Client |
It's client-only, with no server build.
Loaders and versions
- Fabric: Minecraft 1.17 to 26.3. The newest build requires Cloth Config API and Fabric API, optionally Mod Menu; some builds for 1.17 to 1.19.4 require Fabric API; some builds for 1.19 to 1.19.2 need no dependencies.
- Quilt: Minecraft 1.17 to 1.21.1, builds stopped after May 2024. The newest build requires Cloth Config API and Fabric API, optionally Mod Menu; builds for 1.17 to 1.19.4 require Fabric API.
How FastQuit works
Normally, quitting a singleplayer world means waiting for the server thread to fully write chunk data before the title screen loads. FastQuit skips that wait: the world keeps saving in the background while the client unloads its rendered chunks at the same time, so both processes finish sooner even when quitting isn't instant. The saving world still appears on the world list, and it can be renamed, deleted or reloaded while still writing, because FastQuit reads that information from the still-running server session instead of the locked save file. Thread-safety work backs this up; if something does go wrong, the action just fails and Minecraft shows a toast rather than corrupting a save.
Configuration
Options live in the config screen, opened from Mod Menu, or in fastquit-config.txt.
- Show toasts, toggles the pop-up when a world finishes saving in the background.
- Background thread priority, a 0 to 10 value that trades slower saves for smoother gameplay while saving; 0 disables the change.
- Render saving screen, shows the classic saving screen on high render distance setups where unloading chunks still takes a moment.
- Show saving time, displays how long a save took on toasts (1), the world list (2), or neither (0).
Compatibility
Questions about FastQuit.
5 questions
What does FastQuit actually change when quitting a world
It lets the title screen load before a singleplayer save finishes writing, so the world keeps saving in the background instead of freezing the game. Rendered chunks unload on the client at the same time as the background save, so quitting usually finishes faster even when it isn't instant.
Is FastQuit safe to use while a world is saving
FastQuit adds thread-safety handling so background saves, edits, deletes and reloads use the still-running session rather than a locked file. If an action can't complete safely it fails with a toast instead of touching the save.
Does FastQuit need other mods to run
Recent builds need extra libraries to power their configuration screen, while older builds made for earlier Minecraft numbers run with fewer or no extra requirements. Check the specific build's requirements before installing so the game doesn't fail to load.
Can FastQuit run on a multiplayer server
No. FastQuit is client-only, with no build made for dedicated servers. It changes what happens on the client side when leaving a singleplayer world, so there's nothing for a server installation to run.
Does FastQuit work with Mod Menu
Yes, Mod Menu is optional and gives FastQuit an in-game options screen for toasts, thread priority, the saving screen and saving-time display, alongside the Cloth Config API that newer builds also require for that screen. Without Mod Menu, the same options are edited directly in the fastquit-config.txt file.
