Installation

SumatraPDF comes as an installer or as a portable single .exe. Here you can read about downloading, installing (interactive or silent), extracting without installing, where settings go, and fixing failed upgrades.

Download the latest release installer and double-click it. At a glance:

Installer: SumatraPDF-<ver>-install.exe, registers file associations and optional preview handler.
Portable: SumatraPDF-<ver>.exe, a single self-contained .exe.
Silent install: -install -silent.
Extract only: -x -d <dir>, no registration.
Custom settings directory: -appdata <directory>.

Download #

SumatraPDF has two flavors: installer and portable.

Portable (SumatraPDF-<ver>.exe downloaded as SumatraPDF-<ver>.zip) is a single, self-contained .exe.

Installer (SumatraPDF-<ver>-install.exe) installs to %LOCALAPPDATA%\SumatraPDF (or %PROGRAMFILES% with -all-users) and registers file associations. It can also register the optional preview handler.

Install #

Interactive: double-click the installer.
Silent (no installation UI):

  SumatraPDF-<ver>-install.exe -install -silent

Common options (the full list is in Installer cmd-line arguments):

Option	Meaning
`-d <dir>`	Install directory
`-all-users`	Install to `%PROGRAMFILES%\SumatraPDF` for all users (ver 3.4+)
`-with-preview`	Register the File Explorer preview pane handler
`-with-thumbnails`	Register File Explorer thumbnails (ver 3.7+)
`-with-filter`	Register Windows Search PDF filter
`-no-desktop-shortcut`	Don’t create a desktop shortcut (ver 3.7+)
`-log`	Write log to `%LOCALAPPDATA%\sumatra-install-log.txt`

Extract without installing #

SumatraPDF-64-install.exe -x -d "C:\Temp\Sumatra"

The command extracts SumatraPDF.exe, libsumatrapdf.dll, sumatrapdf-tool.exe, etc. into the target directory and does not register file associations. Recent builds do not create Start Menu or desktop shortcuts when extracting only.

Set as default viewer #

After installing, follow Set as default PDF viewer. The portable exe alone does not register defaults.

Use a custom settings directory (enterprise / RDP) #

Launch shortcuts with:

SumatraPDF.exe -appdata "D:\Shared\SumatraSettings"

All users sharing that path use the same SumatraPDF-settings.txt. Ensure the directory is writable by every account that runs SumatraPDF. See Portable vs installed settings for the default locations.

Use the command-line tools #

After a full install, sumatrapdf-tool.exe is next to SumatraPDF.exe and on PATH. With the portable EXE you can run the same commands as SumatraPDF.exe <tool> (see Tools), or extract sumatrapdf-tool.exe with -x, so no install is required.

Tips #

Use -install -silent for unattended deployment, and add -log to diagnose failures.
Use -x to get matching SumatraPDF.exe and libsumatrapdf.dll without touching file associations.
Close Explorer preview panes and stop Windows Search before upgrading if a DLL is locked.
Don’t run SumatraPDF as administrator for everyday reading.

Upgrade fails: file in use (PdfFilter.dll / PdfPreview.dll / libsumatrapdf.dll) #

Through 3.6 the engine DLL was named libmupdf.dll, and from 3.7 it is libsumatrapdf.dll.

When upgrading, the installer renames existing DLLs aside before writing new ones. The rename fails if Windows still has the old file open:

File	Often locked by
PdfFilter.dll	Windows Search (`SearchIndexer.exe`, `SearchFilterHost.exe`) after PDF IFilter registration
PdfPreview.dll	File Explorer preview pane / `dllhost.exe` / `prevhost.exe`
libsumatrapdf.dll	Running SumatraPDF, Explorer preview, or Search filter hosts

Typical Windows errors during install are 32 (sharing violation, file in use) and 5 (access denied on replace or delete).

What the installer does #

Unregisters the search filter and preview handler (if installed)
Stops the Windows Search service (WSearch) when possible
Kills processes that still load install-dir modules
Renames PdfFilter.dll, PdfPreview.dll, and libsumatrapdf.dll to *.copy
If a rename stays blocked, shows a dialog and retries every few seconds until it succeeds or you abort

What you can do #

Close all SumatraPDF windows and other PDF apps
Close Explorer windows that show a PDF preview pane (or turn off the preview pane)
Temporarily stop Windows Search:
- Win+R → services.msc → Windows Search → Stop
- Or elevated: net stop WSearch
Run the installer again (as admin for “all users” under Program Files)
After install, start Windows Search again if you stopped it (net start WSearch)

If the install still fails, reboot and run the installer before opening PDFs or browsing folders with preview enabled.

Corrupted or incomplete installation #

If SumatraPDF reports a corrupted installation:

libsumatrapdf.dll is missing next to SumatraPDF.exe, or
libsumatrapdf.dll version does not match SumatraPDF.exe

Fix: run the official installer, use the portable exe, or extract with -x so both files match.

Also see Failed to load libsumatrapdf.dll if the app starts but cannot load the DLL (often antivirus).

Installer runs when I open a PDF #

SumatraPDF only shows the installer UI when the executable name contains -install (official installers rename themselves that way) or you pass -install. If double-clicking a PDF launches an installer:

File association may point at the installer .exe instead of installed SumatraPDF.exe
You may be running a copied installer from Downloads instead of the installed copy

Re-run the official installer, then check Set as default PDF viewer.

Multiple copies / old versions #

An older SumatraPDF in %LOCALAPPDATA% or a renamed portable copy can confuse file associations. Uninstall via Settings → Apps, then install fresh.

Admin vs normal user #

Do not run SumatraPDF as administrator for everyday reading. An elevated instance cannot open files dropped from a normal Explorer session (“running as admin and cannot open files from a non-admin process”).

Portable vs installed settings #

	Portable	Installed
Settings file	Same folder as `.exe`	`%LOCALAPPDATA%\SumatraPDF\SumatraPDF-settings.txt`
Thumbnail cache	`sumatrapdfcache` next to exe	`%LOCALAPPDATA%\SumatraPDF\sumatrapdfcache`

Override with -appdata <directory>. See Command-line arguments and How we store settings.