The Sift Backport Installation: Versions, Loaders, and Safe Upgrades | The Sift Minecraft
A source-led guide to the community Sift Backport, with compatibility checks, the project-specific /thesift route, installation, upgrades, troubleshooting, backups, and removal boundaries.
The Sift Backport is a separate community Minecraft Java project. Its project-specific documentation is not the same thing as Mojang's future vanilla release, Mielon's The Sift mod, or a Bedrock add-on. This guide shows how to identify the correct file, match the loader and Minecraft version, install it in an isolated profile, and avoid treating /thesift as a universal command.
Direct answer: what is the Sift Backport?
The Sift Backport is the community project published by Zerw on CurseForge. The project page is the authority for its current Minecraft versions, loader, dependencies, file notes, changelog, and any entry instructions. This site has separately recorded that the project documents /thesift; that command belongs to the Backport project and should not be copied into vanilla Minecraft, Bedrock, or Mielon's project.
The official Minecraft position is separate. Minecraft Java status and the release-date page explain that Java and Bedrock are announced for 2027, while an official vanilla entry method has not been published in the cited announcement. A Backport file therefore cannot prove an official release, official recipe, or official compatibility.
Source hierarchy and project identity
Use this order when researching an installation:
- Zerw's Sift Backport page on CurseForge for the current file and project-specific instructions.
- The exact file's version, loader, dependency, and changelog fields.
- The Sift portal troubleshooting guide for warnings about mixing projects.
- Official status for what is and is not confirmed by Mojang sources.
Do not use a search result title, a reposted jar, a video comment, or a screenshot as a substitute for the exact file page. If the author changes the supported version or loader, the old instructions become historical context rather than a current installation recipe.
Source preview
This preview is the official Minecraft Dungeons II source video. It is not a Backport demonstration and does not establish that the Backport implements the same content.

Compatibility matrix
The Backport's compatibility can change with each file. Use the matrix as a decision gate, not as permission to install a neighboring version.
| Check | Safe statement | Required action |
|---|---|---|
| Edition | Community Java project | Do not install it as Bedrock .mcpack/.mcaddon content. |
| Minecraft version | The exact supported release is controlled by the current CurseForge file | Select the file whose version exactly matches your launcher profile. |
| Loader | The current project page/file listing is authoritative | Match the loader named by the file; do not mix Fabric, Forge, NeoForge, or another loader profile. |
| Dependencies | Required libraries, if any, are listed with the exact file | Install only the dependencies listed for that file and version. |
| Entry method | The project documents /thesift as project-specific | Do not run it in vanilla Minecraft or another Sift project. |
| Official status | Not an official vanilla release | Keep community instructions separate from official release claims. |
| World safety | A world may reference mod data after play | Back up before install, upgrade, or removal; test on a copy first. |
No fixed version number is printed here because a static number becomes misleading when the author publishes a new file. The correct number is the one displayed beside the file you choose today. If the project page does not list your launcher version, the answer is “not confirmed for this profile,” not “try the closest file.”
Prepare an isolated installation
The safest setup is a new launcher profile or mod-manager instance. Keep the Backport separate from Mielon's The Sift, other Backports, Bedrock packages, and unrelated content mods. Similar names do not mean shared registries or shared commands.
- Record the launcher profile's Minecraft version, loader, loader version, and Java runtime.
- Open Zerw's current CurseForge page and select the exact file with matching labels.
- Read the file's dependency and relation panels. Record required libraries before downloading anything.
- Create a dated backup of the target world, instance
modsfolder, configuration folder, and launcher settings. - Start the loader profile without the Backport once. This confirms that the base loader is healthy.
- Keep the first test world disposable. Do not begin with a long-running survival save.
This preparation also makes support reports useful. A crash reproduced in a clean profile with one Backport file is actionable; a crash from a profile containing ten untracked jars is not.
Installation steps
1. Select the exact file
On the Zerw CurseForge project page, open the current files and inspect the Minecraft version, loader label, release status, dependencies, and changelog. Use the file's own metadata, not a third-party filename, to decide whether it belongs in your profile.
2. Install the matching loader
Create or select a launcher profile using the loader named by the file. A loader profile is part of the compatibility contract. Do not install an additional loader because another Sift project uses it, and do not put files from different loader ecosystems into one profile.
3. Add dependencies exactly as listed
If the file requires a library, add that library for the same Minecraft and loader version. A missing dependency error is not fixed by adding a random latest build. If the page lists no dependency, do not invent one from a tutorial for Mielon's mod.
4. Add the Backport jar
Place only the selected Backport jar in the profile's mods directory. Remove duplicate downloads, older versions, and similarly named jars from the test profile. Duplicate project jars can produce confusing class and registry errors.
5. Boot and verify identity
Launch the profile and create a temporary world. Confirm that the game reaches the world, the loaded mod list identifies the Backport, and the log does not show a missing dependency or wrong-version error. Only then test the project's documented /thesift route, and only in this Backport profile.
6. Test before migrating a main world
Close and reopen the test world. If the project includes a dimension or content that changes world data, copy the world before any further experiment. A first successful launch is not evidence that an old world will migrate safely.
Using /thesift safely
The /thesift command is a project-specific detail recorded for the Backport. It is not a universal Minecraft command and is not evidence that Mojang has published a vanilla portal. If the command is unknown, first verify:
- the loaded mod list identifies Zerw's Backport;
- the jar matches the current Minecraft version and loader;
- no old or duplicate Sift jar is present;
- the command is documented for the exact file or release;
- you are testing in a world where commands are permitted.
Do not copy /thesift into a vanilla Java profile, a Bedrock world, or a Mielon profile and then report that The Sift is unavailable. That test compares different projects. Use Mielon's installation guide when the intended project is Mielon's mod.
Upgrade procedure
Backport upgrades should be tested as migrations:
- Read the new file's changelog for world, dependency, or command changes.
- Confirm the new file still matches the current launcher version and loader.
- Back up the world and instance before replacing the jar.
- Duplicate the profile and test the new file with a copy of the world.
- Check the log, loaded mod list, and the documented entry path.
- Reopen the copied world after a clean shutdown.
- Promote the new file to the live profile only after the duplicate behaves as expected.
If the upgrade changes a dependency or loader, treat it as a profile migration rather than a simple file swap. If the new file does not support your current world version, preserve the old profile and backup. Do not downgrade a world repeatedly while trying random combinations.
Common errors
The launcher says the mod is for another version
Remove the jar and return to the file list. Choose an exact version match or keep the profile unchanged until the author publishes one. Editing the filename cannot change the compiled target.
The loader rejects the jar
The profile loader and file loader do not match, or the loader version is outside the file's supported range. Build a clean profile from the file's loader label. Do not add Fabric, Forge, and NeoForge to the same profile.
A dependency is missing
Read the exact file's dependency panel and install the named library for the same game version and loader. If the dependency cannot be matched, stop and retain the crash log for the author.
/thesift is unknown
Check the project identity, loaded mod list, command permissions, and exact file notes. The command is not a vanilla command. Do not troubleshoot it by adding Mielon's jar or a Bedrock package.
The command works but the expected content is absent
Confirm that the world was created or opened with the Backport loaded, then check the log and project changelog. A command can exist while a world was generated before the mod, a dependency is stale, or an instruction belongs to another release.
The world crashes after an upgrade
Stop opening the original world. Restore the backup, reproduce with the copied world, and compare the old/new file and dependency lists. Preserve the crash report. Never delete the save to hide a migration failure.
Backup and uninstall boundaries
Before removal, back up the world, mods, config, and launcher profile. Test the removal on a copy. Remove the Backport jar and only its documented dependencies from the copied profile, then launch and inspect the log. If the world references modded dimensions, blocks, items, or entities, removal may not be clean.
The safe boundary is explicit:
- Do not promise that a world will remain unchanged after removal.
- Do not delete mod data folders from the original save without author instructions.
- Do not reuse a world backup from a different Minecraft version as if it were interchangeable.
- Keep the original profile available until the copied-world test is complete.
- Follow the author's migration notes when they exist; otherwise, stop at backup and ask for project-specific guidance.
FAQ
Is the Backport an official Minecraft release?
No. It is a community Java project. Official status is covered separately on this page.
Can I use the Backport on Bedrock?
No. Bedrock add-ons use different package formats and compatibility rules. Use the Bedrock installation page for that platform.
Is /thesift a vanilla command?
No. It is documented as a Backport-specific route. A command from a community project cannot establish an official vanilla entry method.
Which exact Minecraft version should I install?
Choose the version printed beside the current CurseForge file you select. This article intentionally avoids freezing a number that may become stale.
Can I combine the Backport with Mielon's The Sift?
Do not assume compatibility. They are separate projects with separate files and potentially overlapping content. Test them in separate profiles unless the author explicitly documents interoperability.
Where should I download it?
Start at Zerw's CurseForge project. Avoid re-upload mirrors and links that do not identify the author or file metadata.
What should I include in a bug report?
Include the exact Minecraft version, loader, loader version, Backport file, dependencies, latest log, crash report, and reproduction steps. Do not upload private worlds or personal launcher credentials.
Related pages
- What is The Sift?
- Mielon's The Sift compatibility and installation
- Portal troubleshooting
- Java Edition status
- Bedrock installation notes
- Community project directory
Sources
Related Guides
Blub Minecraft Guide: Mielon's The Sift Mod
Find out what the Blub is in Mielon's The Sift mod, including its neutral behavior, Soul Block attraction, and taming notes.
Charoite in Mielon's The Sift: How to Verify It Safely | The Sift Minecraft
A source-led guide to checking whether Charoite is present in Mielon's The Sift, matching the right file and loader, testing it safely, and avoiding invented recipes or drop rates.
How do I choose a compatible Mielon's The Sift file | The Sift Minecraft
A source-led answer about How do I choose a compatible Mielon's The Sift file?
How do temporary Rifts work in Mielon's The Sift | The Sift Minecraft
A source-led answer about How do temporary Rifts work in Mielon's The Sift?