PDFMergeX Support

Get help with PDFMergeX, report a problem, or suggest an improvement. Support is provided by Bartlomiej Budzynski, the individual developer publishing PDFMergeX under the display name B2BB.

You can write in English or Polish.

Getting started

Select at least two PDF files in Windows File Explorer, right-click them, and choose Merge selected PDF files. With a Polish Windows display language, the command is Scal zaznaczone pliki PDF.

The merged document is saved beside the first input file as merged_YYYYMMDD_HHMMSS.pdf. A completion dialog shows the output path. Launching the app from Start shows instructions; use File Explorer to select your documents.

Troubleshooting

The context-menu command is missing

Make sure every selected item is a PDF file and that at least two files are selected. The command is hidden for a single file or a mixed selection. Installation registers the command automatically. If it remains missing after installation or an update, restart Windows Explorer or sign out and back in.

The app cannot open a PDF

Check that the files still exist and can be read from their current location. For a synchronized folder or network share, make sure the files are available locally or through the network. Try a small set of non-sensitive sample PDFs to see whether the problem is specific to one document.

A PDF that requires a password to open cannot be merged: PDFMergeX has no password-entry interface. Corrupt or invalid PDFs may also cause the merge to fail.

The output file already exists

PDFMergeX refuses to overwrite an existing file, including an input PDF. Choose a new output filename when using the command line. With automatic timestamp-based naming, wait until the next second before trying again, or move the previous output to another location.

The output file cannot be created

Check that the output folder exists, that Windows allows you to create files there, and that the drive has enough free space. The application writes to a temporary file in that folder before publishing the completed PDF.

The documents appear in the wrong order

PDFMergeX uses the order supplied by Explorer, which may differ from the order in which you clicked the files. To set the order explicitly, pass the input paths in the desired order on the command line. Pages within each input PDF retain their original order.

What happens to forms, bookmarks, signatures, and encryption?

The merge engine preserves page content, sizes, annotations, and interactive form fields. It resolves conflicting field names when copying forms. Check the resulting document, particularly when it contains complex forms.

Document-level bookmarks and digital signatures are not preserved. PDFMergeX does not encrypt the output. Keep your original signed or encrypted documents.

Are my files uploaded?

PDFMergeX processes PDFs locally and does not upload them for merging. Files in OneDrive or other synchronized folders may be transferred independently by those services. The local diagnostic log is not uploaded automatically.

Command-line usage

These PowerShell examples use the executable from the installed Microsoft Store package. The package does not declare a command-line alias, so a bare pdfmerge command may not be available on your PATH.

$package = Get-AppxPackage -Name B2BB.PDFMergeX
if (-not $package) { throw "PDFMergeX is not installed for this user." }
$pdfMergeExe = Join-Path $package.InstallLocation 'pdfmerge.exe'

# Merge in the supplied order, next to the first input file.
& $pdfMergeExe 'C:\Documents\first.pdf' 'C:\Documents\second.pdf'

# Choose a new output filename in an existing folder.
& $pdfMergeExe --output 'C:\Documents\combined.pdf' 'C:\Documents\first.pdf' 'C:\Documents\second.pdf'

Put --output before the input filenames. Paths containing spaces should be quoted. The application adds .pdf when the output path does not already have that extension. It also accepts --output=PATH; -- ends option parsing. The command-line mode still shows completion or error dialogs.

To find the installed package version for a support request:

Get-AppxPackage -Name B2BB.PDFMergeX | Select-Object Name, Version, Architecture

Diagnostic log

The application writes a local diagnostic log at:

%LOCALAPPDATA%\PDFMerge\pdfmerge.log

Enter this path in File Explorer’s address bar. Windows package redirection may affect its physical location.

The log records timestamps, startup events, successful output paths, and error messages. Paths and error details can reveal your Windows username or document names. Review and redact a log before sharing relevant lines by email. The form below accepts text only.

The log is not uploaded automatically and has no automatic expiration or rotation. You can delete it; later use of the app may recreate it.

What to include in a support request

• The PDFMergeX package version and Windows version.
• Whether you used the Explorer command or the command line.
• Steps to reproduce the issue, the expected result, and what happened instead.
• The exact error text, with personal paths or sensitive details removed.

Please omit passwords and sensitive document contents. Redact screenshots before attaching them to an email. Send a sample PDF only if requested, and use a non-sensitive example where possible.

For Microsoft account, billing, refund, or Store download issues, contact Microsoft Support. For PDFMergeX behavior or errors, contact the developer using the support form.

Privacy

Information you choose to send is used to respond to your request as described in the PDFMergeX Privacy Policy. Avoid including documents or sensitive information unless needed to resolve your request.