- Enable UseTabs and ReuseInstance, then restart SumatraPDF completely.
- Compare internal file opening with File Explorer launch behavior.
- Check shortcuts, duplicate installations, processes, and settings persistence.
When SumatraPDF tabs are not working, the symptom usually falls into one of four categories: tabs are disabled, documents are being sent to separate SumatraPDF processes, a shortcut or command-line flag is forcing a new window, or the settings file is not preserving your changes. The quickest solution is to test two ordinary local documents from inside SumatraPDF, verify the UseTabs and ReuseInstance settings, restart the application completely, and then compare that behavior with files opened from File Explorer.
This guide focuses on the tab interface and document windows. Format-specific rendering components, document permissions, and external tools matter only when they prevent a file from opening normally. Follow the steps in order and stop as soon as two documents consistently open as tabs in one SumatraPDF window.

Start with free Canva bundles
Browse the freebies page to claim ready-to-use Canva bundles, then get 25% off your first premium bundle after you sign up.
Free to claim. Canva-ready. Instant access.
1. Confirm the Symptom With a Simple Document Test
Before changing settings, determine whether tabs fail everywhere or only when files are opened in a particular way. This distinction prevents unnecessary changes to Windows associations or SumatraPDF's configuration.
1.1 Test two documents from inside SumatraPDF
Open SumatraPDF directly from the Start menu or its executable file. Then use the application's Open command to open a small, ordinary local PDF. Repeat the same process with a second local PDF while leaving the first document open.
If both documents appear across the top of one window, the tab interface is working. The problem is probably limited to File Explorer, a desktop shortcut, another application, or a command that launches SumatraPDF. Stop changing the UseTabs setting and proceed to the launch-method checks.
If the second document replaces the first, opens in a separate window, or produces no visible tab, continue to the settings checks below. Use uncomplicated local files for this test. Avoid network shares, email attachments, password-protected documents, and unusual formats until basic tab behavior is confirmed.
1.2 Check whether more than one process is running
Open Windows Task Manager and look for SumatraPDF processes after opening two documents. Multiple visible windows can sometimes belong to separate processes rather than separate tabs within one process.
Do not end processes immediately if they contain documents you still need. First close SumatraPDF normally, wait a few seconds, and check Task Manager again. If a process remains, close it only after confirming that no unsaved annotations or other work could be affected.
Success means opening two test documents produces one normal SumatraPDF window with selectable tabs. Once that happens, no process cleanup or configuration reset is necessary.
2. Check the Settings and Commands That Control Tabs
Two advanced settings are especially relevant to this symptom. UseTabs controls whether documents can appear in tabs, while ReuseInstance helps new open requests reach an existing SumatraPDF instance instead of creating another one.
2.1 Verify UseTabs and ReuseInstance
In SumatraPDF, open the Settings menu and select Advanced Options. This opens the active SumatraPDF-settings.txt file in a text editor. Find the relevant lines and verify that they are set as follows:
- UseTabs = true
- ReuseInstance = true
Keep the existing formatting and change only the value after the equals sign. Do not create duplicate entries if the setting already exists. A duplicate or malformed line can make troubleshooting harder because it may be unclear which value is being applied.
Save the file, close every SumatraPDF window, verify that no SumatraPDF process remains, and start the application again. A full restart is important because changing the visible setting does not necessarily rebuild every open window immediately.
Success means two documents opened from within the restarted application occupy separate tabs in the same window. If this works, stop editing the settings file.
2.2 Check tab switching shortcuts
After opening at least two documents in tabs, press Ctrl+Tab to move to the next tab. Press Ctrl+Shift+Tab to move in the opposite direction. Test these shortcuts while the document area has focus, not while a menu, search box, dialog, or another application is active.
If clicking tabs works but Ctrl+Tab does not, the tab feature itself is functioning. The issue is more likely keyboard focus, a remapped shortcut, an accessibility utility, remote desktop behavior, or software intercepting the key combination. Test with the on-screen tabs first, then close dialogs and try the shortcut again.
If the shortcut changes tabs but no tab bar is obvious, inspect the top of the window and maximize it temporarily. The Home tab or start page may also affect what you expect to see when no document is selected.
2.3 Understand Home tab behavior
The Home tab is SumatraPDF's start interface, commonly used for recently opened or frequently accessed documents. It is not evidence that document tabs are broken. Depending on the current state and configuration, opening or closing documents can expose the Home view again.
For a reliable test, keep one document open and then open a second document. Do not judge tab support solely by whether the Home tab remains visible. Success is demonstrated by switching between two open documents without creating separate windows.
2.4 Remove commands that force new windows
SumatraPDF can be launched with command-line arguments. A shortcut, script, file manager, launcher, or other application may use the -new-window argument, which intentionally requests a separate window. That behavior can override the workflow you expect from normal tab reuse.
Right-click any shortcut used to open SumatraPDF, select Properties, and inspect the Target field. The executable path may be quoted, but unnecessary arguments after the path should be reviewed. If -new-window is present, make a backup copy of the shortcut and remove that argument for a controlled test.
Do not remove arguments you do not understand from managed workplace shortcuts. In that situation, create a temporary plain shortcut to SumatraPDF.exe and test with it instead.
Success means launching documents through the corrected shortcut reuses the existing window and creates tabs. If opening from inside SumatraPDF already works, this launch-path correction may be the only fix required.
3. Compare File Explorer and External Launch Behavior
If tabs work from SumatraPDF's Open command but fail when you double-click files, the reader's core tab interface is healthy. Focus on the Windows file association and the command used by the external source.
3.1 Test the Windows file association
Set SumatraPDF as the default application for the affected file type through Windows Settings or the Open with dialog. Then close all reader windows, start SumatraPDF normally, open one document inside it, and double-click a second document of the same type in File Explorer.
If the second file becomes a tab, the association is passing the request correctly. If it creates a new window, compare the result with another supported extension. For example, test two PDFs before assuming that a comic archive, CHM file, image, or eBook format has the same association behavior.
Reinstalling SumatraPDF can recreate associations, but it should not be the first step. Re-selecting the default application is faster and preserves your current configuration.
3.2 Distinguish document problems from tab problems
A document that fails to render, requests a password, is damaged, or uses an unsupported feature can make the tab workflow appear inconsistent. However, that does not normally mean tabs themselves have failed.
- If an ordinary PDF opens in a tab but one specific file does not, investigate that file.
- If one format fails while PDFs work, check format support and any component required for that format.
- If a file opens only from a temporary email or browser location, save it locally and test again.
- If Windows denies access, copy the file to a folder you can read and retry without changing document restrictions.
Some formats or tasks may depend on external components, codecs, Ghostscript, printer drivers, or another application. Those factors are relevant when opening, rendering, converting, or printing fails. They are not the first suspects when two ordinary PDFs simply open in separate windows.
Never attempt to bypass document permissions or digital rights management as part of tab troubleshooting. Use a document you are authorized to access and test with an unrestricted local file instead.
3.3 Check installed and portable copies
Windows users sometimes have both an installed copy of SumatraPDF and a portable executable. Each copy may use a different settings location and may therefore have different values for UseTabs and ReuseInstance.
From the window exhibiting the problem, open Advanced Options and confirm which settings file appears. Also check the executable path through Task Manager or the shortcut's Properties dialog. If File Explorer launches the installed copy while your desktop shortcut launches the portable copy, changing settings in one will not necessarily fix the other.
Success means every launch method points to the intended executable and that executable reads the settings file you edited. Once the paths match, stop changing unrelated Windows settings.

4. Inspect or Reset SumatraPDF-settings.txt Safely
A settings-file reset is appropriate when UseTabs or ReuseInstance will not stay enabled, Advanced Options opens an unexpected file, changes disappear after restarting, or the file contains duplicate or damaged configuration entries.
4.1 Back up the active settings file
Open Advanced Options from the affected SumatraPDF window. In the text editor, use Save As or Windows File Explorer to make a copy named something recognizable, such as SumatraPDF-settings-backup.txt. Store it outside the active configuration folder.
Close all SumatraPDF windows before renaming or replacing the active file. SumatraPDF can write settings as it exits, so editing or deleting the file while the application is still running may cause your changes to be overwritten.
4.2 Check whether settings persist
Set UseTabs and ReuseInstance to true, save the file, and close the editor. Exit SumatraPDF normally, reopen it, return to Advanced Options, and confirm that both values remain true.
If they revert, check whether the settings file or its folder is read-only, whether security software is controlling access, or whether you edited a file belonging to another SumatraPDF copy. Avoid changing broad folder permissions unless you know why access is blocked.
Success means the values remain intact after a complete exit and restart. At that point, test two documents again before performing a reset.
4.3 Reset only when persistence or corruption is suspected
With SumatraPDF fully closed, rename the active SumatraPDF-settings.txt file rather than permanently deleting it. Start SumatraPDF and allow it to create a fresh configuration. Enable tabs if necessary, restart once more, and repeat the two-document test.
A fresh settings file also resets unrelated preferences, including display and history choices. That is why renaming is safer than deletion. If the reset does not help, you can close SumatraPDF and restore the backup.
If tabs work with the fresh file, reapply only the preferences you actually need. Do not immediately copy the entire old file back, because that can restore the setting conflict.
5. Run a Clean Temporary Test Before Reinstalling
A clean test separates a program-level problem from a Windows association, shortcut, or configuration problem. The portable edition is useful for this purpose because it can be placed in a temporary folder and tested without replacing the installed copy.
5.1 Test one executable with two local files
- Close all existing SumatraPDF windows.
- Confirm in Task Manager that no SumatraPDF process remains.
- Start the clean or portable executable directly, without a custom shortcut.
- Verify UseTabs and ReuseInstance.
- Restart that same executable.
- Open two ordinary local PDFs from inside the application.
- Test Ctrl+Tab and Ctrl+Shift+Tab.
- Open a third file from File Explorer and observe which executable receives it.
If the first two files become tabs but the File Explorer file opens elsewhere, Windows is launching a different installed copy or association command. If all files become tabs, the clean configuration is working and reinstalling is unnecessary.
If even the clean executable opens two ordinary PDFs in separate windows, recheck that no -new-window argument is involved and that the settings were saved before restart. Document the exact launch sequence before seeking support.
5.2 Reinstall only after the clean test
Reinstallation can help when executable files or registered associations are damaged, but it does not automatically repair a conflicting portable copy, a custom shortcut, or a settings file that remains in the user profile. Preserve a backup of your settings before uninstalling.
After reinstalling, launch SumatraPDF directly, confirm tab settings, restart, and test internally before restoring custom shortcuts. This order reveals whether each restored component reintroduces the problem.
6. Quick Fix Checklist
- Open two ordinary local PDFs from inside SumatraPDF first.
- Set UseTabs to true in Advanced Options.
- Set ReuseInstance to true when you want one reusable application instance.
- Save the settings file and restart every SumatraPDF window.
- Confirm no leftover SumatraPDF process remains before retesting.
- Use Ctrl+Tab and Ctrl+Shift+Tab only after two tabs are open.
- Do not confuse the Home tab with an open document tab.
- Remove -new-window from personal shortcuts when it is not wanted.
- Compare opening files internally with double-clicking them in File Explorer.
- Verify that installed and portable copies are not using different settings.
- Rename and regenerate the settings file only if changes do not persist.
- Stop troubleshooting as soon as two documents consistently share one window.
7. Frequently Asked Questions
7.1 Why does SumatraPDF open every PDF in a separate window?
The most likely causes are disabled tabs, disabled instance reuse, multiple SumatraPDF copies, or a shortcut containing -new-window. Set UseTabs and ReuseInstance to true, restart completely, and test from inside the application. If internal opening works, inspect File Explorer associations and shortcuts.
7.2 Why does Ctrl+Tab do nothing?
Ctrl+Tab requires multiple open tabs and the appropriate application focus. Click the document or a visible tab, close active dialogs, and try again. Ctrl+Shift+Tab should switch in the reverse direction. If mouse-based switching works, the problem is with keyboard handling rather than tabs.
7.3 Do I need to restart SumatraPDF after enabling tabs?
Yes, a complete restart is the safest test. Close every window, ensure no process remains, and reopen the application. This confirms that the setting was saved and that a new window was created using the updated configuration.
7.4 Why do tabs work inside SumatraPDF but not from File Explorer?
This usually indicates a Windows association or launch-command issue. File Explorer may be starting another installed or portable copy, or its registered command may request a new window. Re-select SumatraPDF as the default application and verify which executable opens.
7.5 Should the Home tab disappear when a document opens?
Not necessarily. The Home view is a start interface, not a reliable test of whether document tabs work. Open two documents and verify that you can select each one within the same window.
7.6 Will reinstalling fix SumatraPDF tabs not working?
It may repair damaged installation files or associations, but it will not necessarily correct a custom shortcut, a second portable copy, or persistent settings. Run a clean temporary test first. Reinstall only if the clean test or association checks point to an installation problem.