Rehoboth Builds

Export and import

Overview  ·  Actions  ·  Site rules  ·  Export & import  ·  Permissions  ·  FAQ

Your settings are a file you own. This page exists because the most common complaint about the extension we set out to replace was that an update wiped everyone's shortcuts with no way to get them back.

Export

Select Export to file on the options page. You get a JSON file named for the day you exported it:

keyboard-shortcuts-2026-08-30.json

It contains your shortcuts, their actions, their site rules, your preferences, a random id per shortcut (so the extension can tell your own rules apart) and the time you exported. It contains no user identifier, no history, and nothing about the pages you have visited. You can open it in any text editor and read all of it.

Import

Select Import from file and choose a previously exported file. There is one checkbox that changes what happens:

SettingResult
Merge with existing unchecked (default) The imported file replaces everything you currently have.
Merge with existing checked Imported shortcuts are added to what you already have.

Undo an import

Before any import is written, the extension automatically snapshots your previous settings in your own browser. If you imported the wrong file, select Undo last import and your previous state comes back.

Use it straight away. There is one snapshot slot, and it is overwritten before any change — adding a shortcut, editing one, toggling one off. So the button restores whatever came before your most recent change, which is the import only if you have not touched anything since.

The snapshot lives in your browser's local storage. It is not synced and never leaves your device.

Moving to another machine

Shortcuts sync automatically through your own Chrome profile — if you are signed into the same profile on two computers, both see the same shortcuts without any export. Export is for the cases sync does not cover: a different browser profile, a work machine you are not signed into, or a backup you want to keep yourself.

Schema version

Exported files carry a schema version. Future versions of the extension will migrate older files forward rather than rejecting them, and migration is additive — an upgrade will not drop settings it does not recognise.