Keybind Sync

Keybind Sync

You already set Minecraft up the way you like it. Then you install a new modpack, and it is all gone — every binding back to default, brightness back to 50%, subtitles off, your server list empty.

Keybind Sync keeps your setup in one folder shared by every instance on your PC, and keeps your packs in step while you play. Change your FOV in one pack, and every other pack you have open has it a couple of seconds later.

Set up in one step

Open Options → Controls → Key Binds, press Profiles, type a name and press Save new.

That is it. The first profile you save becomes the default and live sync is on, so every pack you launch from then on starts with your setup, and every change you make in one reaches the rest.

What it carries

Everything is optional. The What to sync screen has a switch for each group.

That is every setting the game exposes as an option — 106 of them on 1.21.11.

Live, and careful about it

• Only what you change travels. A pack shares the settings you actually changed, one by one, and takes only the ones another pack changed. Two packs changing different settings at the same moment both keep their change.
• Nothing lands mid-load. Changes wait for the loading screen to finish, and your server list only changes where no screen is holding a copy of it.
• It never shares what the game did by itself. When a pack finishes loading, the game adjusts a few settings to your graphics card. Those stay in that pack.
• Saves are locked, so two games writing at the same instant cannot drop each other's change.

Prefer to press a button? Switch Auto to On edit and packs catch up with your profile when they start, or to Off and nothing happens unless you press Load.

Works in any launcher

It runs inside the game, so Prism, MultiMC, CurseForge, ATLauncher, the Modrinth App and the official launcher all behave the same. Profiles are plain JSON files in %APPDATA%/keybindsync (~/.config/keybindsync on Linux, ~/Library/Application Support on macOS). Nothing goes online. Point KEYBINDSYNC_DIR at a synced folder to have the same setup on a second PC.

Every binding, whatever the mod called it

Most mods name their keys key.something, but not all do — Essential's emote wheel and chat peek are two that do not. Keybind Sync carries every binding the game registers, under its own name, so those follow you too.

It handles packs that are not the same

• Mods a pack does not have keep their entries in the profile untouched. Saving from a light pack never wipes the bindings you set up in a heavy one.
• Mods the profile has not seen keep their own defaults. Nothing is unbound behind your back.
• Settings that changed between versions are converted by the game's own code or skipped, never forced. menuBackgroundBlurriness was a 0–1 fraction in 1.20.6 and a 0–10 integer from 1.21.1; loading a newer profile on an old version skips that one and applies the rest.
• Hotbars follow you to packs on the same or a newer version, and Minecraft upgrades the items itself, enchantments and all. An older version keeps its own, because it cannot read a newer file.
• Servers are matched by address. The ones a pack ships with stay; the ones you add follow you.

Several profiles, and packs that want their own

Keep as many profiles as you like — one for PvP, one for building — and Load any of them in any pack. The default is the one packs follow.

A pack that should keep its own setup gets This pack: Own: nothing is applied to it, and nothing you change in it is shared.

Mod settings

Tick config files from a list and they ride along, copied byte for byte — any format works, nothing is parsed. Mods read their config while they start up, so these are restored before any mod initialises, which is the only point where it takes effect the same session.

• A config written for one version of a mod is not always valid for another. Tick files deliberately, a few at a time, rather than everything at once.
• Anything a restore replaces is copied to config/keybindsync-backups/ first. Nothing is ever deleted.

What it deliberately leaves alone

• Performance settings, unless you switch them on. A render distance that is comfortable in a light pack can be miserable in a heavy one, so the distances stay with each pack by default. On 1.21.11 and newer, applying a graphics preset puts them back as they were too.
• Fullscreen — which monitor you play on is not something a shared profile should decide.
• Sound device — that names a sound card on your machine, not a preference.

Using your launcher's settings sync too?

If your launcher can also sync options.txt (the Modrinth App can, since version 0.20), pick one of the two for game settings. Both would end up agreeing, but two tools writing the same file makes it hard to tell which one changed what.

Compatibility

• Client side only. It does nothing on a server and is safe to use on any of them.
• No Fabric API needed.
• Every Minecraft release from 1.19 to 26.2. Pick the download whose range covers your pack.

If another mod rewrites the Key Binds screen and the Profiles button does not appear, syncing still works — the button is a convenience, not the mechanism.