Open-source project
pdfarranger/pdfarranger avatar
pdfarranger/pdfarranger

PDF Arranger: a pikepdf front end for reordering PDF pages

Small python-gtk application, which helps the user to merge or split PDF documents and rotate, crop and rearrange their pages using an interactive and intuitive graphical interface.

6,051 stars330 forksPythonGPL-3.0

At a glance

What is it?
A small GTK application that merges, splits, rotates, crops and rearranges PDF pages by driving pikepdf. Cheap to install from a distribution, but the dependency lists differ and image import needs a second package.
Who is it for?
Use PDF Arranger when the job is page level: rotating and cropping a scan, deleting pages, splitting one file into several, or merging several into one. Do not treat it as a general PDF editor, and skip the virtual environment route if you need a fixed version, because pip installs from zipball/main, which tracks the branch tip rather than the 1.14.0 tag.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • pdfarranger/pdfarranger6,051 ★ · +131
Star history
Repository2026-09-232026-11-15
pdfarranger/pdfarranger5.9k6.1k

131 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A GTK window that never parses a PDF itself

PDF Arranger does not read PDFs. It is a GTK window that asks pikepdf to do the reading. The project describes itself as a small python-gtk application for merging or splitting PDF documents and for rotating, cropping and rearranging their pages, and it names its engine plainly: it is a front end for pikepdf.

That division shows up at install time. The application requires pikepdf >= 6, a constraint the project carries rather than your distribution's package database, and pip will install the latest pikepdf automatically when the system has none. A pip-based install therefore drags a compiled dependency along with it, whether you wanted one or not.

The visible feature list stays short while the dependency surface does not. What the documentation describes is page surgery on files you already have: rotate the pages that came out of a scanner sideways, drop the blanks, cut one file into pieces, join pieces back together. Nothing in that description covers text editing, annotation, or filling forms, and the user manual in the project wiki is where the interface details live.

The fork line runs back to PDF-Shuffler

PDF Arranger is a fork of Konstantinos Poulios's PDF-Shuffler, whose own project pages sit on Savannah and Sourceforge. The fork states its motive in one line: it is a humble attempt to make the project a bit more active. The attribution survives in the source, where the header of setup.py carries a copyright line for Konstantinos Poulios dated 2008-2017.

So PDF-Shuffler is not a rival to weigh. It is the parent tree, and the practical question when choosing between them is which one receives the work. The tags visible here are 1.14.0 from 2026-05-23, 1.13.0 from 2026-02-01 and 1.12.1 from 2025-06-11, and the last push to the repository was on 2026-11-01.

The licence is GPL-3.0, with the licence text in the COPYING file at the top level and the version 3 or later notice in the setup.py header. Derived builds carry that licence forward; the documentation says nothing about relicensing, so treat redistribution questions as a matter for the licence text itself rather than for this repository.

Four dependency lists, and they are not the same list

The install-from-source section gives a different command for each distribution, and the differences are not cosmetic. Arch Linux gets one flat pacman line. The Debian family needs pip, wheel, gobject, the GTK 3, poppler 0.18 and handy typelibs, python3-setuptools, gettext, python3-dateutil and python3-venv. Fedora adds python3-pikepdf and python3-img2pdf. FreeBSD spells the same ideas as devel/gettext, devel/py-gobject3, devel/py-pip, graphics/poppler-glib, textproc/py-pikepdf, x11-toolkits/gtk30 and x11-toolkits/libhandy.

Arch Linux, in one line:

bash
sudo pacman -S poppler-glib python-pip python-gobject gtk3 python-cairo libhandy

Notice what that line leaves out: no wheel, no setuptools, no gettext, no dateutil, no venv. The README carries four blocks instead of one. The Debian list also never names python3-pikepdf, which is the reason for the sentence about pip installing pikepdf on its own.

Ubuntu takes the Debian line, then one pip step

On Ubuntu and Debian the README hands you a single apt-get call with shell continuations. This is the route to use when the application should live on the system rather than inside a throwaway environment:

bash
sudo apt-get install python3-pip python3-wheel python3-gi python3-gi-cairo \
    gir1.2-gtk-3.0 gir1.2-poppler-0.18 gir1.2-handy-1 python3-setuptools \
    gettext python3-dateutil python3-venv

The typelib packages carry the widget layer and page rendering, and gettext and the po directory behind it handle translation. The roles of python3-dateutil and python3-venv are not spelled out; the second one is what makes the environment route in the next section possible at all.

What this list does not do is install the application. After the dependencies are in place, the source still has to arrive, and the venv route is the shortest documented way to do that on a Debian-family system.

The venv route installs a moving target

The virtual environment route deserves a careful read, because the version it installs is not a release. The environment is created at /home/user/myenv with system site packages enabled, pip installs the archive of the main branch, and a symlink then puts pdfarranger on the path:

bash
python3 -m venv --system-site-packages ~/myenv
~/myenv/bin/pip3 install --upgrade https://github.com/pdfarranger/pdfarranger/zipball/main
sudo ln -s ~/myenv/bin/pdfarranger /usr/local/bin/pdfarranger

The --system-site-packages flag is the load-bearing part. It lets the environment see the GTK and poppler libraries the distribution installed, which is exactly why the apt-get line above and this environment can cooperate instead of conflicting.

The URL is the other half of the story: zipball/main resolves to whatever sits on the main branch at the moment you run it, so two people following the same three lines a month apart can end up with different code. The 1.14.0 tag is a fixed alternative, and the releases page on GitHub is where a Windows build and the tagged sources are published.

Image import lives in another project

Image import is the feature most likely to surprise you, because it is not part of the application. PDF Arranger supports importing image files if img2pdf is installed, and the README links that project on its own GitLab page. A stock install therefore gives you a page editor for PDFs and nothing wider; putting img2pdf on the system is what extends the open dialog past PDF.

Only one of the four dependency lists mentions it. The Fedora command includes python3-img2pdf, while the Debian, Arch and FreeBSD commands do not. That asymmetry is the clearest sign in the documentation that image import is an opt-in dependency rather than a bundled feature, and it is the first thing to check if your file dialog refuses a JPEG.

Packaging shows the same asymmetry. The downloads table points at the GitHub releases for Windows, at Flathub as com.github.jeromerobert.pdfarranger, and at snapcraft.io/pdfarranger, with a wiki page collecting further binary packages. macOS gets a sentence and a file: for macOS see macOS.md. No packaged macOS build appears anywhere in that table.

One repository, four build systems

The tree carries a build definition per download route, and each one is a single top-level file. pdfarranger.spec is the RPM spec used by Fedora-style packaging. snapcraft.yaml defines the Snap behind the snapcraft.io entry. setup_win32.py and Win32.md cover Windows, whose download is the releases page rather than a package. Distributions that ship their own build are tracked through the Repology link, and TESTING.md, .coveragerc, .prospector.yaml and tests/ cover the test and lint side.

The packaging logic sits in setup.py, and its data_files list is short enough to read in one pass. A desktop entry goes to share/applications, pdfarranger.ui and menu.ui go to share/pdfarranger, the man page doc/pdfarranger.1 goes to share/man/man1, and the AppStream metadata file goes to share/metainfo.

One compatibility shim is worth knowing about, because it fails quietly. The script parses the installed setuptools version and, below (65, 2), imports the build command from distutils instead of setuptools. On an old distribution that is the difference between a working build and an import error.

Translation work has one forbidden file

Localisation reaches into four places. Interface strings live in po/LANG.po. Repository and desktop integration carry their own files, data/com.github.jeromerobert.pdfarranger.metainfo.xml and data/com.github.jeromerobert.pdfarranger.desktop. Native language names for the preferences drop-down come from LANGUAGE_NAMES in pdfarranger/config.py.

The contribution sequence is fixed, and translations can also be edited directly from the web interface if git is not your tool:

bash
git checkout -b update-translation-LANG
po/updatepo.sh LANG

Edit po/LANG.po, then open a pull request against main. The one rule with teeth is about po/pdfarranger.pot: do not commit changes to it, because it may have been regenerated automatically and your edit would be noise in the diff. Mnemonic keys, the letters preceded by an underscore, follow GTK and GNOME practice: stay consistent with other GTK software, pick a unique letter within the menu where you can, reuse the original letter when it exists, and prefer a strong letter, so Search and replace takes s, r or p rather than a.

Editorial conclusion

Use PDF Arranger when the job is page level: rotating and cropping a scan, deleting pages, splitting one file into several, or merging several into one. Do not treat it as a general PDF editor, and skip the virtual environment route if you need a fixed version, because pip installs from zipball/main, which tracks the branch tip rather than the 1.14.0 tag. Before building from source, check two things: whether your distribution's list already includes img2pdf, since only the Fedora line names it and the others leave image import off, and whether your setuptools is at least (65, 2), below which setup.py falls back to distutils. On a Linux desktop with no need for source builds, the Flathub package com.github.jeromerobert.pdfarranger or the Snap at snapcraft.io/pdfarranger is the shorter route.

Frequently asked questions

What is PDF Arranger?

It is a small python-gtk application for merging or splitting PDF documents and for rotating, cropping and rearranging their pages, and it is a front end for pikepdf, which it requires at version 6 or newer. It is a fork of Konstantinos Poulios's PDF-Shuffler.

How do I install PDF Arranger?

The project gives a dependency command per distribution for a source install, and a virtual environment route that installs from the main branch archive with pip. Packaged builds come from Flathub as com.github.jeromerobert.pdfarranger, from snapcraft.io/pdfarranger, or from the GitHub releases page on Windows.

How do I install PDF Arranger in Ubuntu?

Ubuntu is covered by the Debian-based list: python3-pip, python3-wheel, python3-gi, python3-gi-cairo, the GTK 3, poppler 0.18 and handy typelibs, python3-setuptools, gettext, python3-dateutil and python3-venv. The application itself then arrives through pip. Importing image files needs img2pdf on top, which that list does not name.

How do I use PDF Arranger?

The interface details live in the user manual in the project wiki. What the README covers is the scope: merging or splitting PDF documents and rotating, cropping and rearranging pages, with a cloned working copy for development.

Is a PDF arranger free?

PDF Arranger is free software under the GPL-3.0, with the licence text in the COPYING file at the top level of the repository and the version 3 or later notice repeated in the header of setup.py.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. pdfarranger/pdfarranger on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pdfarranger-pdfarranger.svg)](https://hysenlabs.com/projects/pdfarranger-pdfarranger)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pdfarranger-pdfarranger.svg)](https://hysenlabs.com/projects/pdfarranger-pdfarranger)

Was this useful?