PDF Arranger describes itself as a front end for pikepdf, the library that does the actual reading and writing of PDF files underneath the interface. That is why, if saving or exporting fails, the message you see may mention pikepdf rather than PDF Arranger itself. Users have reported save failures traced to the pikepdf layer in the project’s issue tracker, so you are not alone, and the steps below are the sensible order to work through them.
Step 1: Update everything first
Start with the current release: PDF Arranger 1.14.0 (May 23, 2026), from our download page on Windows, or through Flathub or your distribution on Linux. Newer releases ship with newer pikepdf versions, and that matters beyond bug fixes: the outline-preserving export introduced in 1.14.0 requires pikepdf 8.0 or newer. If you installed from source, make sure your pikepdf meets the version requirements in our Linux dependency guide. Retest the same export after updating; a large share of save failures disappear at this step.
Step 2: Suspect the source file, not just the app
An export can fail because one of the input files is damaged in a way that only shows up when the file is rewritten. Test it: open the source PDF in another PDF tool and save a fresh copy from there, then import that copy into PDF Arranger and repeat your edits. Re-saving rebuilds the file’s internal structure. If the fresh copy exports cleanly, the original file was the cause, and you have lost nothing but a few minutes.
Step 3: Find the problem page by splitting the export
If you are exporting many pages and the failure keeps happening, export in two halves instead of all at once. If one half succeeds and the other fails, split the failing half again. A few rounds of this usually narrow the problem down to a single page or a single source file. You can then leave that page out, re-create it from its original document, or handle it in a separate export and merge the results afterwards. This is slower than a single export, but it turns a mystery failure into a localised one.
Step 4: Use a rasterized export as a fallback
PDF Arranger can also export a rasterized PDF, in which each page is rendered as an image inside the PDF, and can export pages as PNG or JPEG images. If a normal export fails but you need the document today, a rasterized export is a reasonable fallback: it takes a different code path that does not depend on copying the original page structure across. Be aware of the trade-offs before you rely on it: text in a rasterized export is no longer selectable or searchable, and the file is often larger. Keep your project in the normal format as well, so you can re-export properly once the underlying problem is fixed.
Step 5: Check the destination
As a general check, make sure the folder you are saving to is writable and has free space, and that the target file is not currently open in another program that might be locking it. Saving to a new filename in a different folder rules all of this out in one test.
Still failing? Report it with the details that matter
Search the official GitHub Issues tracker and, if your case is new, open an issue. The useful details are your PDF Arranger version, how pikepdf was installed if you know it, your operating system, and exactly which export you attempted when the failure occurred. If a sample file reproduces the failure and contains nothing private, attaching it helps more than any description.