Install PDFsam Basic 6.0.5

Windows

Paste into the Run box (Win+R), PowerShell or Windows Terminal:

winget install -e --id PDFsam.PDFsam --accept-source-agreements --accept-package-agreements
  1. Press Win+R
  2. Paste with Ctrl+V
  3. Press Enter

Package: winget package PDFsam.PDFsam, which installs the official PDFsam Basic MSI from GitHub.

Or download the file directly from the official release:

Download Windows x64 MSI pdfsam-basic-6.0.5-windows-x64.msi · 93.8 MB · August 5, 2026

Also on this release: Windows x64 ZIP (no installer)

Verify the download (SHA-256)

GitHub publishes this hash for pdfsam-basic-6.0.5-windows-x64.msi. It must match exactly.

956c37e2bbb1ac8af73f6aa2bc1dc651d457274221522e27e512d725b703f002

PowerShell: Get-FileHash .\pdfsam-basic-6.0.5-windows-x64.msi -Algorithm SHA256

64-bit (x64) Windows. Java is bundled with the app, so nothing else is needed. Installs for all users to C:\Program Files\PDFsam Basic.

macOS

Paste into Terminal, with Homebrew installed:

brew install --cask pdfsam-basic

Package: Homebrew cask pdfsam-basic, which downloads the official DMG from GitHub.

Or download the file directly from the official release:

Download macOS DMG for Apple silicon pdfsam-basic-6.0.5-macos-arm64.dmg · 93.6 MB · August 5, 2026

Also on this release: macOS DMG for Intel Macs

Verify the download (SHA-256)

GitHub publishes this hash for pdfsam-basic-6.0.5-macos-arm64.dmg. It must match exactly.

61a1644dbe71b063e8b302c430e4285daf29c8013bdd729e7c3592cf9d0a915a

Terminal: shasum -a 256 pdfsam-basic-6.0.5-macos-arm64.dmg

Apple silicon DMG by default; Intel Macs take the x64 DMG. Drag PDFsam Basic to Applications.

Linux

Paste into a terminal, in the folder with the downloaded .deb:

sudo apt install ./pdfsam-basic_*_amd64.deb

Package: the official .deb from the GitHub release, installed with apt so dependencies resolve.

Or download the file directly from the official release:

Download Debian and Ubuntu .deb (x64) pdfsam-basic_6.0.5-1_amd64.deb · 96.5 MB · August 5, 2026

Also on this release: Linux x64 tar.gz for other distributions

Verify the download (SHA-256)

GitHub publishes this hash for pdfsam-basic_6.0.5-1_amd64.deb. It must match exactly.

99cf8fc0ea49dadc3420e2b4989358b02089f762cd9f8d9ef17ea53da2779919

Terminal: shasum -a 256 pdfsam-basic_6.0.5-1_amd64.deb

64-bit Debian, Ubuntu or a derivative for the .deb; the tar.gz runs on other distributions. Installs to /opt/pdfsam-basic.

Every file comes from github.com/torakiki/pdfsam, the project's own v6.0.5 release, unmodified.

PDFsam Basic Merge tool before any file is added, with the Drag and drop PDF files here area, Merge settings and Destination file
PDFsam Basic 5.2 interface: the Merge tool before adding files, with Merge settings and the Destination file below the empty list. PDFsam Basic 6.0.5 keeps the same eight tools and the same Merge settings. Frame from the PDFsam Basic README animation in the torakiki/pdfsam repository (Sober Lemur S.r.l.).

How do I get winget working?

It takes five steps: check for winget, install App Installer, open a new window, install PDFsam Basic and accept the agreements once.

  1. Check for winget. Open PowerShell or Windows Terminal and run winget --version.
  2. Install App Installer. If the command is not recognised, open the Microsoft Store page for App Installer and click Get or Update.
  3. Open a new window. Close PowerShell and open a new window so it picks up the winget command.
  4. Install PDFsam Basic. Paste the PDFsam Basic winget command from the install box and press Enter.
  5. Accept the agreements once. The two accept flags in the command answer winget's agreement prompts, so the install runs unattended.

Why is winget missing?

winget ships inside App Installer, which Windows updates through the Microsoft Store. It can be missing on a fresh install that has not updated Store apps yet, on Windows 10 builds older than 1809, on Windows Server, and on PCs where an administrator has disabled the Store. Updating App Installer fixes the first two; on managed PCs, ask the administrator or use the MSI from the Windows download page.

winget problems and fixes
SymptomLikely causeFix
winget is not recognisedApp Installer missing or outdatedInstall or update App Installer from the Microsoft Store, then open a new window
No package found matching input criteriaTypo in the id or a stale sourceRun winget source update and paste the command again
Installer hash does not matchDamaged download or a replaced release fileRun the command again; if it repeats, use the MSI and check its hash yourself
A newer version is already installedThe MSI refuses downgradesNothing to do, or uninstall first if you really need the older release

What does the PDFsam Basic winget command do?

winget install -e --id PDFsam.PDFsam --accept-source-agreements --accept-package-agreements looks up the exact package id PDFsam.PDFsam in Microsoft's community repository and downloads the MSI that the package manifest names on GitHub. It checks the file against the recorded SHA-256 and runs it silently with /quiet /norestart SKIPTHANKSPAGE=Yes. The two --accept flags agree to the source and package terms, and -e stops winget matching a similarly named package.

How do you update or remove PDFsam Basic with winget?

Run winget upgrade -e --id PDFsam.PDFsam to move to the newest release, or winget upgrade --all to update everything winget manages. To remove the app, run winget uninstall -e --id PDFsam.PDFsam. Uninstalling removes the program from Program Files; PDFs you split or merged stay wherever you saved them.

Frequently asked questions

Is winget safe to use?

winget is Microsoft's package manager. Each manifest records the download URL and SHA-256 of the installer, and winget refuses a file whose hash does not match.

Can I use winget without the Microsoft Store?

Yes. Microsoft also publishes App Installer as an msixbundle on the winget-cli GitHub releases page, which installs directly on PCs without Store access.

Does the Win+R method work for winget?

Yes. The Run box starts winget in its own console window, which closes when the install finishes. Use PowerShell instead if you want to read the output.