SumatraPDF Opens Every File in a New Window: How to Fix It

If SumatraPDF opens every file in a new window, the problem usually comes from the interaction between tab support, instance reuse, and the command used to launch the reader. Enabling tabs alone may not solve it because each document can still start a separate SumatraPDF process. The steps below help you identify the exact cause without reinstalling immediately, deleting settings blindly, or changing unrelated Windows options.

1. Confirm the Symptom With a Simple Two-Document Test

Start by confirming how SumatraPDF behaves when Windows launches two ordinary PDF files. This separates a general SumatraPDF configuration problem from an issue caused by a particular shortcut, application, or document format.

1. Close every visible SumatraPDF window.
2. Open Task Manager by pressing Ctrl+Shift+Esc.
3. Look for remaining SumatraPDF processes and close them if no documents are still being used.
4. In File Explorer, double-click one local PDF.
5. Return to File Explorer and double-click a second local PDF.

Use simple PDFs stored on the local drive for this test. Avoid email attachments, browser downloads that open through a temporary handler, and files launched from a document-management program. Those sources may use their own commands.

1.1 What the test results mean

If both PDFs appear as tabs in one SumatraPDF window, the reader itself is behaving correctly. The original problem is probably limited to the shortcut, browser, external program, or file type that launched the other documents. Stop changing SumatraPDF's global settings and inspect that launch source instead.

If the second PDF opens in another window, check Task Manager. Two separate SumatraPDF processes indicate an instance-reuse or launch-command problem. One process with multiple windows points more directly to window or tab configuration.

Success at this stage means two PDFs opened from File Explorer remain in one SumatraPDF window, normally as separate tabs. Once that happens, do not reset or reinstall the application unless the behavior returns through another launch source.

2. Check UseTabs and ReuseInstance Together

The two settings most closely related to this symptom are UseTabs and ReuseInstance. They solve different parts of the problem.

• UseTabs controls whether multiple documents can be displayed as tabs within a window.
• ReuseInstance tells later launches to reuse an existing SumatraPDF instance instead of starting an independent one.

Tabs cannot combine documents across separate running processes. If every file launch starts another process, enabling tabs may appear to do nothing. SumatraPDF must first route the new document to an existing instance before that document can appear in the existing window's tab bar.

2.1 Enable tabs in SumatraPDF

Open SumatraPDF and look under its settings or options for the tab-related preference. Ensure tabs are enabled. Depending on the release and interface, the visible option may be presented as using tabs or opening documents in tabs.

The underlying advanced setting is normally written as:

UseTabs = true

After changing UseTabs, close all SumatraPDF windows and start the program again. A complete restart matters because the tab setting is not necessarily applied to windows or processes that were already running.

Then repeat the two-PDF File Explorer test. Success means the second document becomes another tab in the existing window. If it still creates a separate process, continue to instance reuse.

2.2 Check instance reuse

Open SumatraPDF's advanced settings and locate the ReuseInstance line. For the behavior described here, set it to:

ReuseInstance = true

Save the settings, close all SumatraPDF windows, and verify in Task Manager that no SumatraPDF process remains. Restart the program and repeat the two-document test.

ReuseInstance is particularly important when a file association, shortcut, script, or external program launches SumatraPDF.exe again for every document. With reuse enabled, the later launch can hand the file to the already running instance rather than leaving a second independent reader process open.

Stop changing settings as soon as two File Explorer launches open in the same window. If the test succeeds but files from one particular application still open separately, the remaining issue is that application's launch command.

3. Inspect Commands, Shortcuts, and File Launches

SumatraPDF supports command-line options that can explicitly request a new window or reuse an existing instance. A shortcut or external tool can therefore override the behavior you expected from the normal interface.

3.1 Remove the new-window flag

Inspect any shortcut, script, launcher, browser integration, or document manager that starts SumatraPDF. Look at the command used to open the file. If it contains the following option, that option is directly relevant:

-new-window

The -new-window flag deliberately requests a new SumatraPDF window. Remove it when the goal is to open subsequent documents in the existing reader window.

For a Windows shortcut, right-click the shortcut, select Properties, and inspect the Target field. Do not remove the path to SumatraPDF.exe or placeholders used to pass the document name. Remove only the unwanted new-window option.

3.2 Use the reuse-instance flag when needed

If an external application supports a configurable PDF viewer command, the following flag can request reuse:

-reuse-instance

A typical command conceptually consists of the path to SumatraPDF.exe, the reuse flag, and the document path supplied by the external program. Keep paths in quotation marks when they contain spaces.

Do not combine -new-window with -reuse-instance and expect predictable single-window behavior. The options express conflicting intentions. Remove -new-window first, then use -reuse-instance if the launching tool repeatedly starts the executable.

3.3 Compare direct and external launches

Run the same document through two routes:

1. Open it normally from File Explorer.
2. Open it from the browser, email client, reference manager, search tool, or other application where the problem occurs.

If File Explorer reuses the window but the external application does not, SumatraPDF's general settings are probably correct. Examine the viewer command configured in that external application. Success means both launch routes send documents to the same SumatraPDF instance, or you have confirmed that only the external tool needs adjustment.

4. Check Windows and Installation Factors That Actually Matter

This symptom is not usually caused by PDF rendering, codecs, Ghostscript, printer drivers, or document restrictions. Those factors can affect whether content displays or prints correctly, but they do not normally decide whether two readable PDFs share a SumatraPDF process.

4.1 File associations can contain launch options

The important file-association question is not simply whether SumatraPDF is the default PDF reader. If the files already open in SumatraPDF, the basic default-app choice is working. The relevant question is whether the registered open command includes an option such as -new-window or points to a different copy of SumatraPDF.

For example, an older portable copy and an installed copy might both exist on the computer. One file type could launch the installed executable while a shortcut launches the portable executable. Because they are different executables with different settings locations, their windows may not be reused as expected.

Check the path shown in the shortcut's Target field and compare it with the executable you normally run. Task Manager can also help identify the executable location. Avoid editing the Windows Registry as a first step. Correcting the shortcut, external-tool command, or SumatraPDF registration is safer.

4.2 Installed and portable copies keep settings differently

An installed SumatraPDF setup generally keeps user settings in the user's local application data area. A portable setup can keep its settings beside the executable. If you edit one settings file but launch another copy, your changes will appear to have no effect.

To verify the active copy, open SumatraPDF's advanced settings from the running application rather than locating a file through Windows search and guessing. This opens the settings associated with that copy.

Success means there is one intended SumatraPDF executable handling the tested documents and its settings contain the expected tab and reuse values.

4.3 Source documents and formats

Repeat diagnosis with two ordinary local PDFs before testing eBooks, comic archives, CHM, DjVu, XPS, images, or other supported formats. Different file types can have separate Windows open commands even when they all use SumatraPDF.

If two PDFs share a window but two files of another type do not, inspect the association or external command for that specific extension. The document's permissions or restrictions may affect reading, copying, or printing, but they should not be bypassed and are generally unrelated to instance reuse.

5. Inspect or Reset SumatraPDF-settings.txt Safely

If UseTabs or ReuseInstance will not remain changed, inspect the active SumatraPDF-settings.txt file. A persistence problem can make SumatraPDF return to the same behavior after every launch.

5.1 Back up and edit the active settings file

1. Open advanced settings from within the SumatraPDF copy you actually use.
2. Note the settings file that opens.
3. Close every SumatraPDF window.
4. Confirm through Task Manager that no SumatraPDF process remains.
5. Make a backup copy of the settings file.
6. Open the original in a plain-text editor.
7. Find UseTabs and ReuseInstance.
8. Set them to true, save the file, and restart SumatraPDF.

Closing SumatraPDF before editing is important. A running process may write its in-memory configuration back to disk when it exits, overwriting manual changes.

Do not create duplicate setting lines unnecessarily. Edit the existing entries when they are present. Also check whether the file is read-only or whether the current Windows account lacks permission to save in that location.

5.2 Reset only when the settings appear damaged

If the file contains unexpected duplicate entries, cannot be parsed normally, or changes never persist despite correct permissions, close SumatraPDF and rename the file rather than deleting it. For example, rename it to SumatraPDF-settings-backup.txt.

Start SumatraPDF so it can create a fresh settings file. Re-enable tabs, confirm instance reuse, restart again, and perform the two-PDF test. Renaming is safer than deletion because bookmarks, history, favorites, display preferences, and other configuration data may be recoverable from the backup.

If the fresh file fixes the issue, stop there and restore only settings you actually need. Copying the entire old file over the new one can restore the original problem.

6. Run a Clean Temporary Test Before Reinstalling

A clean test determines whether the behavior belongs to the existing configuration or to the way Windows launches SumatraPDF. It is more informative than immediately reinstalling, because uninstalling may leave user settings untouched.

1. Close all SumatraPDF processes.
2. Create an empty temporary folder for test settings.
3. Launch the same SumatraPDF executable with its supported -appdata option pointing to that folder.
4. Enable tabs in the clean instance if they are not already enabled.
5. Close and restart that test instance after changing UseTabs.
6. Open two PDFs through the clean test instance or invoke the executable with -reuse-instance for both test launches.

This test should use the same executable each time and must not include -new-window. If the clean environment reuses one window, the installed program files are probably fine. The cause is more likely the normal settings file, a second SumatraPDF copy, or a launch command.

If even the clean test starts independent processes, review the exact command and confirm that each launch uses the same executable and app-data location. Reinstallation is reasonable only after those details have been checked. A reinstall cannot correct a third-party shortcut that continues to pass -new-window.

7. Quick Fix Checklist

• Close every SumatraPDF window and end leftover SumatraPDF processes.
• Test two local PDFs by double-clicking them separately in File Explorer.
• Set UseTabs = true.
• Fully restart SumatraPDF after changing UseTabs.
• Set ReuseInstance = true when repeated launches create separate processes.
• Remove -new-window from shortcuts and external viewer commands.
• Use -reuse-instance where an external tool supports a custom command.
• Confirm all launches point to the same installed or portable executable.
• Edit settings only while SumatraPDF is completely closed.
• Rename and regenerate the settings file before considering a reinstall.

The fix is complete when two PDFs opened from File Explorer appear in one SumatraPDF window, usually as separate tabs, and Task Manager does not show an unnecessary process for each file. At that point, stop changing global settings. Troubleshoot only the specific application or file type that still behaves differently.

8. Frequently Asked Questions

8.1 Why does enabling tabs not stop separate windows?

Tabs organize documents inside one SumatraPDF process or reusable window. They cannot merge documents when every launch creates an independent process. Close extra processes, enable ReuseInstance, and remove any -new-window option from the launch command.

8.2 Do I need to restart SumatraPDF after enabling UseTabs?

Yes. Close all SumatraPDF windows and confirm that no background process remains before reopening it. A full restart ensures the tab setting is applied to a newly created application instance.

8.3 What is the difference between UseTabs and ReuseInstance?

UseTabs controls the presentation of multiple documents within a window. ReuseInstance controls whether a later program launch hands its document to an already running instance. For reliable tabbed behavior, both the interface configuration and the launch behavior must be compatible.

8.4 Why does File Explorer work while my browser opens new windows?

The browser or its download handler may use a separate command, temporary launcher, or different SumatraPDF executable. If the two-PDF File Explorer test succeeds, leave the working global settings alone and inspect the browser or external viewer configuration.

8.5 Will reinstalling SumatraPDF fix separate windows?

Not necessarily. Reinstallation may not remove user settings, repair a portable copy, or change an external application's command. Test UseTabs, ReuseInstance, process cleanup, launch flags, and a clean settings location first.

8.6 Are Ghostscript, codecs, or printer drivers responsible?

They are unlikely to cause this exact symptom. Rendering components and printer drivers matter when a document cannot display or print correctly. When documents display normally but each one opens in a separate window, focus on instance reuse, tabs, executable paths, and launch commands.