SumatraPDF Custom Keyboard Shortcuts Not Working: How to Fix Them

When SumatraPDF custom keyboard shortcuts are not working, the cause is usually a malformed Shortcuts entry, an invalid command name, a duplicate key assignment, an unsaved settings file, or editing a different settings file from the one your current SumatraPDF installation uses. The fastest solution is to test one simple binding in a controlled document, confirm that SumatraPDF accepts the settings syntax, and then restore your other customizations gradually. This guide focuses specifically on user-defined shortcuts, not failures involving SumatraPDF's normal built-in keyboard commands.

1. Confirm the Symptom With One Simple Test

Before changing several settings, determine whether SumatraPDF is rejecting all custom shortcuts or only one particular command and key combination. Open a simple local PDF that you know works correctly. Avoid beginning with a password-protected document, a file opened from an email attachment, or an unusual format because those factors can obscure the result.

1.1 Verify That Built-In Keyboard Input Still Works

Press a familiar built-in key, such as an arrow key for navigation or Ctrl+O for opening a file. The exact built-in behavior can depend on the current view and focus, but the goal is to confirm that SumatraPDF receives keyboard input at all.

If built-in keys work while your newly defined key does nothing, focus on the custom shortcut definition and settings persistence. Reinstalling immediately is unlikely to help because the application itself is already receiving input.

1.2 Test Only One Custom Shortcut

Temporarily reduce the Shortcuts array to one carefully checked entry. Choose a command that produces an obvious result and a key combination that is not already used by SumatraPDF, Windows, your keyboard utility, or another application. Use a command name listed in SumatraPDF's official command documentation rather than guessing one from the menu label.

A shortcut definition follows this general structure:

Shortcuts [
  [
    Cmd = CmdOpenFile
    Key = Ctrl+Shift+O
  ]
]

The command above is only a diagnostic example. If the official command list for your installed build uses a different name, use the documented name exactly. Command identifiers are not free-form descriptions.

Save the file, close every SumatraPDF window, start the application again, and test the key. Success means the assigned action occurs consistently in the relevant context. Once that happens, stop changing unrelated settings. Add your remaining shortcuts back one at a time so that any defective entry is easy to identify.

2. Check the Shortcut Definition Directly

A custom shortcut is recognized only when its structure, command identifier, and key value can be parsed. A visually small mistake can cause an entry to be ignored or can prevent the edited settings from surviving a restart.

2.1 Check the Shortcuts Array Syntax

The outer Shortcuts [ ] block contains individual shortcut records. Each record also uses square brackets and normally contains one Cmd line and one Key line. Check the following details:

• The outer Shortcuts block has both an opening and closing bracket.
• Every individual shortcut record has its own matched bracket pair.
• Cmd and Key appear inside the same record.
• No copied record contains a missing or extra closing bracket.
• The block is not accidentally nested inside an unrelated settings section.
• The original Shortcuts block was edited instead of creating conflicting copies elsewhere.

Bracket pairing mistakes are particularly easy to introduce when several shortcuts are pasted together. To isolate one, remove or temporarily store all but a single record outside the active settings file. If one record works, rebuild the array incrementally.

2.2 Validate Cmd Names

The value after Cmd = must be a command identifier SumatraPDF recognizes. Menu captions, translated interface labels, descriptive phrases, and command names borrowed from another program are not interchangeable with SumatraPDF command identifiers.

Copy the identifier from the official SumatraPDF commands reference when possible. Preserve its spelling and capitalization. Also remember that some commands are meaningful only in a particular state. For example, a page-navigation action needs an open document, while a command associated with a specific document type may not have a visible effect in every format.

Success means the command produces its expected action when tested in an appropriate document and view. If the same key works after you substitute another documented command, the original Cmd value or its operating context is the likely problem.

2.3 Validate Key Values

The Key value must use a notation accepted by SumatraPDF. Use conventional modifier names and key names shown in the official shortcut documentation. Avoid creative labels such as a keyboard manufacturer's marketing name, a localized key caption, or a text character that requires an undocumented notation.

For troubleshooting, prefer a straightforward combination using Ctrl, Shift, or Alt with a letter. Type the combination consistently, without adding quotation marks unless the current documentation explicitly shows them. Function keys, punctuation keys, media keys, AltGr combinations, and keys processed by keyboard-management software are less suitable for an initial test.

If a simple letter-based combination works, the settings mechanism is functioning. Stop resetting SumatraPDF and investigate whether the original key name or physical key is intercepted before it reaches the reader.

2.4 Find Duplicate Shortcuts

Search the full settings file for the proposed key combination. Also compare it with SumatraPDF's built-in shortcuts and your other custom entries. Two custom records that assign the same key to different commands create ambiguity, and a custom key that overlaps with a built-in action may not behave as expected in every context.

Change the test binding to an uncommon combination and restart SumatraPDF if required. If the new combination works, keep one unambiguous assignment or deliberately choose another key. Do not continue editing command names when the evidence points to a collision.

3. Check Context, Windows, and Document Factors

Custom shortcuts are settings-level features, but the assigned action can still depend on application focus, document type, permissions, or external components. Separate a shortcut that is not recognized from a recognized command that cannot complete its task.

3.1 Make Sure SumatraPDF Has Keyboard Focus

Click inside the document area before testing. A search box, page-number field, dialog, menu, annotation field, or other text-entry control can consume keystrokes. If the shortcut works after returning focus to the document, the definition is valid and no settings reset is necessary.

Windows-level utilities can also intercept combinations globally. Common examples include screen-capture tools, graphics-driver overlays, clipboard managers, keyboard remappers, accessibility software, and manufacturer hotkey applications. Test an alternative key combination before disabling software. If the alternative works, resolve the global conflict rather than reinstalling SumatraPDF.

3.2 Test the Command in the Right Document Format

SumatraPDF can display several formats, including PDF, eBook, comic, CHM, DjVu, XPS, images, and supported document formats. Not every command has a useful effect in every format or viewing mode. A command related to pages, printing, document properties, or navigation may be unavailable or behave differently when the current file lacks the required capability.

Test first with a small, ordinary local PDF. Then test the original file. If the shortcut works in the simple PDF but not in the original document, the key binding has loaded successfully. The remaining issue concerns command applicability, document structure, or file permissions rather than shortcut syntax.

3.3 Distinguish Shortcut Failure From External Tool Failure

File associations determine which program opens a document when it is launched from File Explorer, but they normally do not determine whether a custom shortcut is parsed. Similarly, codecs or rendering components are relevant only if the assigned command depends on content that SumatraPDF cannot render. Ghostscript may matter in workflows involving PostScript files, but it does not normally control recognition of a general keyboard binding.

Printer drivers matter when the custom key invokes printing and the print dialog fails, hangs, or produces an error. In that case, test the same print operation from SumatraPDF's menu. If both the menu and custom shortcut reach the same failure, the shortcut works and the printer, driver, spooler, or document is the next troubleshooting target.

Document permissions can restrict actions such as printing or copying. Do not attempt to bypass those restrictions. Test the same command through the menu and use a document for which you have the necessary permissions. If both methods are unavailable, changing the shortcut cannot grant the missing capability.

3.4 Account for Installed and Portable Copies

Windows users sometimes have both an installed copy and a portable copy of SumatraPDF. Each can use a different settings location. A file association or pinned taskbar shortcut may launch one copy while you edit settings associated with another.

Confirm which executable is running. You can launch the intended executable directly, open its advanced settings from within that instance, make a harmless visible change, save, and restart that same executable. If the visible change appears only in one copy, you have identified separate settings environments.

Success means the custom binding works when the exact executable whose settings you edited is launched. At that point, update your file association or shortcut if you want Windows to use that copy consistently.

4. Inspect or Reset SumatraPDF-settings.txt Safely

If the shortcut disappears after saving or restarting, settings persistence is the central issue. Work carefully because SumatraPDF-settings.txt can contain preferences unrelated to keyboard shortcuts.

4.1 Back Up Before Editing

Close SumatraPDF, locate the settings file used by the relevant installed or portable instance, and copy it to a safe location. Give the backup a recognizable name such as SumatraPDF-settings-backup.txt. Do not keep an extra file under the active settings filename in the same location.

A backup lets you recover themes, display preferences, remembered files, and other customizations if a syntax error or reset causes unexpected changes.

4.2 Confirm the File Was Actually Saved

After editing, use the editor's Save command and check for errors. Then reopen the file independently and verify that your Shortcuts block is still present. Watch for these common problems:

• The editor saved a copy in Documents instead of overwriting the active file.
• The filename gained a hidden extension such as .txt.txt.
• The file or folder is read-only.
• Windows permissions prevented the edit from being written.
• A cloud-sync or security tool restored an older copy.
• Another running SumatraPDF window overwrote the manual edit when it closed.

For that last reason, close all SumatraPDF windows before making an external edit. After saving, launch SumatraPDF and test. If the entry remains in the file after another clean shutdown, persistence is working.

4.3 Use SumatraPDF's Advanced Settings Entry Point

When available in your build, opening advanced settings from SumatraPDF helps identify the file the running instance expects. This is safer than finding a similarly named file through Windows Search and assuming it is active.

Do not edit the settings file while multiple SumatraPDF processes or windows remain open. A running process may retain older settings in memory and write them back during shutdown.

4.4 Reset Only After Preserving the Original

If a one-entry Shortcuts block still disappears or is ignored, rename the active settings file while SumatraPDF is closed. Do not delete it. Start SumatraPDF so it can create fresh settings, close the program, and then add one validated shortcut to the newly generated file.

If the shortcut works with the fresh file, the old settings contained a structural conflict or damaged entry. Restore other customizations selectively rather than copying the entire old file over the working one. Stop once the required shortcut and essential preferences work.

5. Run a Clean Temporary Test

A clean test separates an application problem from a settings-location or configuration problem without destroying your current setup. It should come before reinstalling because reinstalling may leave the same user settings in place.

5.1 Create an Isolated Test

1. Back up the active settings file.
2. Close every SumatraPDF window and confirm no related process remains open.
3. Use a clean portable copy obtained from the official SumatraPDF website, or temporarily rename the current settings file.
4. Launch the clean instance directly rather than through a file association.
5. Open a small local PDF.
6. Add one shortcut using an officially documented command and a simple unused key.
7. Save, close the instance completely, reopen it, and test again.

If the shortcut works both before and after reopening, SumatraPDF's shortcut feature is functioning. The original problem lies in the previous settings file, the wrong executable or settings location, or a conflict in the original shortcut array.

If the shortcut works until restart but then disappears, inspect write permissions and confirm where that instance stores its settings. If it remains in the file but does not run, recheck the command identifier, key notation, focus, and command context.

5.2 Reinstall Only When the Clean Test Also Fails

Reinstallation is reasonable only after a clean configuration fails with a documented command and simple key combination. Download SumatraPDF from its official website, verify that you are launching the new executable, and repeat the single-shortcut test before restoring old settings.

Do not immediately copy the entire old SumatraPDF-settings.txt into the new environment. Doing so can reintroduce the exact syntax or persistence problem you are trying to eliminate.

6. Quick Fix Checklist

• Open a simple local PDF and confirm built-in keyboard input works.
• Back up SumatraPDF-settings.txt before making changes.
• Keep only one shortcut record during the first test.
• Match every outer and inner square bracket.
• Copy the Cmd identifier from official SumatraPDF documentation.
• Use a simple, correctly formatted Key combination.
• Search for duplicate custom and built-in key assignments.
• Save the active settings file, not a copy in another folder.
• Close all SumatraPDF windows before external editing.
• Restart the application when testing settings loaded at startup.
• Click the document area so a field or dialog does not capture the key.
• Confirm that installed and portable copies are not being confused.
• Test the command from the menu to separate binding failure from action failure.
• Rename rather than delete the settings file when performing a reset.
• Restore old settings gradually after the clean shortcut works.

7. Frequently Asked Questions

7.1 Why Does My Custom Shortcut Disappear After Restarting SumatraPDF?

The most likely explanations are that the wrong settings file was edited, the edit was not saved, the folder was not writable, or a running SumatraPDF process rewrote the file with its older in-memory settings. Close every instance, edit the file associated with the intended executable, save it, reopen it in your editor to verify the change, and then start SumatraPDF again.

7.2 Does SumatraPDF Need to Be Restarted After Editing Shortcuts?

When editing SumatraPDF-settings.txt externally, the safest procedure is to close all SumatraPDF windows before editing and restart afterward. This ensures the application reads the revised settings and prevents an older running instance from overwriting the file. Once the shortcut works after a full restart, persistence is confirmed.

7.3 Can Two Commands Use the Same Custom Key?

Avoid assigning the same key combination to multiple commands. Duplicate definitions make the outcome ambiguous and can interact with built-in actions or context-specific behavior. Give each custom command a unique key while troubleshooting. If uniqueness fixes the symptom, keep the nonconflicting assignment.

7.4 Why Does the Shortcut Work in a PDF but Not Another Format?

The shortcut may be loaded correctly while its command is unavailable or irrelevant in the second format. Test the equivalent command through SumatraPDF's menu. If neither method performs the action, investigate format support, document state, or permissions. Do not keep rewriting a shortcut that already works in an appropriate document.

7.5 Will Reinstalling SumatraPDF Fix Custom Shortcuts?

Not necessarily. Reinstalling may preserve the same user settings, and it does not correct an invalid Cmd, malformed bracket structure, duplicate key, or edited portable configuration. Run a clean one-shortcut test first. Reinstall only if a fresh configuration and documented shortcut also fail.

7.6 When Should I Stop Changing Settings?

Stop when one documented command works with one simple key, survives a full restart, and works in the appropriate document context. At that point, the custom shortcut system is operating normally. Any remaining failure is specific to the original key, command, document, focus state, external utility, or action such as printing. Change only that isolated factor instead of resetting the entire application.