For a free and universal alternative you can use the pdfbook script, part of the pdfjam collection which is usually included in LaTeX distributions (notably MacTeX). It's simple to use from the command line:
pdfbook mypdf.pdf
If the above doesn't work, then /Library/TeX/texbin isn't in your PATH (or /usr/texbin for older versions of MacTeX). The best course of action is to ensure PATH is correctly set (lots of command line programs will fail if the PATH variable isn't correct and pdfbook is one of them); this isn't trivial under OS X if you want a consistent behavior between applications launched from the dock and applications run from a terminal so you definitely should search a complete solution to this specific problem. As dirty work-around, you can run export PATH="$PATH:/Library/TeX/texbin:/usr/texbin" every time before you use pdfbook (including in the service below).
If you don't want to use the command line, you can create a service easily.
- Launch Automator (on Yosemite it's in Applications/Others)
- Create a new document and select "Service".
- On top of the right frame, for "Service receives selected" choose "PDF files".
- Search "Run Shell Script" from the bar on the top of the left frame and double-click it. Select to "Pass input" as "arguments" in the newly created window.
- Enter a simple script running
pdfbook, for instance pdfbook "$@".
- Save it as "Create booklet" (for instance).
- In Finder, select a PDF file, then in the menu go to Services/Create booklet.
My complete script also creates a temporary file and opens the resulting PDF:
TMPF=`mktemp -t bookletXXXX`
mv "$TMPF" "$TMPF.pdf"
pdfbook -o "$TMPF.pdf" "$@"
open "$TMPF.pdf"
The most obvious problem is the several GB download and installation of a LaTeX distribution if all you want is the pdfbook script.
pdfbookis there so it definitely looks like a PATH problem. Sadly, you can't just use the full path of the script (which is/usr/texbin/pdfbook) because then it will fail to find its parent scriptpdfjam. I've updated my answer with an explanation of the problem and a dirty work-around, but you definitely should fix the PATH problem globally instead (I don't remember how I did it and couldn't find the SO question I used back then but it's there somewhere). – Blout Jun 16 '15 at 17:03brew cask install mactexThis includes a tool calledpdfbook2which seems to do the same aspdfbookin this answer (possibly with different arguments though). As above, you need to start a new shell to update yourPATHvariable. – Rob Jul 07 '20 at 17:19pdfbookhas indeed been superseded bypdfbook2. Also, it’s neat that you can now use homebrew, back when I wrote the answer they would redirect you to the MacTeX website. @Rob, can you edit the answer with the correct paths and such? I no longer have access to a Mac to test it properly. – Blout Jul 13 '20 at 17:42