- It puts merging, reordering, rotating, duplicating, deleting, - inserting, and splitting in one page grid, so you can do several of - them in a single pass without downloading and re-uploading between - steps. Every action is covered by undo and redo, so you can - experiment before you export. -
-- Upload all the source files and their pages appear together in one - grid, in upload order. Drag pages into the order you want, delete - the ones you don't need, and click Export PDF to download the result - as a single file. -
-- Drop JPG, PNG, WebP, HEIC, TIFF, BMP, GIF, or SVG files alongside - your PDFs and each image becomes a page you can move, rotate, or - delete like any other. Blank A4 pages can also be appended with the - Add Blank Page button. -
-- Click the scissors icon on a page to place a split marker after it; - a dashed line shows where the document will be divided. Export then - produces split-documents.zip containing document - 1.pdf, document - - 2.pdf, and so on. -
-- No. Rotation is stored as a page attribute in 90-degree steps rather - than re-rendering the content, so text, vectors, and images are - untouched. For angles other than 90, 180, or 270 degrees, use - Rotate by Custom Degrees. -
-- Tick the checkboxes on the pages you want and use Download selected - to get just those pages as selected-pages.pdf. The workspace stays - as it is, so you can keep working and export the rest later. -
-- The export rebuilds the document page by page, so bookmarks from the - source files aren't carried into the new PDF. Page content, - including text and images, is copied as-is. -
-- No. Page thumbnails are rendered and the final PDF or ZIP is - assembled in your browser, and damaged files are repaired locally - before loading too. Nothing you drop into the grid leaves your - computer. -
-+ It puts merging, reordering, rotating, duplicating, deleting, + inserting, and splitting in one page grid, so you can do several + of them in a single pass without downloading and re-uploading + between steps. Every action is covered by undo and redo, so you + can experiment before you export. +
++ Upload all the source files and their pages appear together in + one grid, in upload order. Drag pages into the order you want, + delete the ones you don't need, and click Export PDF to download + the result as a single file. +
++ Drop JPG, PNG, WebP, HEIC, TIFF, BMP, GIF, or SVG files + alongside your PDFs and each image becomes a page you can move, + rotate, or delete like any other. Blank A4 pages can also be + appended with the Add Blank Page button. +
++ Click the scissors icon on a page to place a split marker after + it; a dashed line shows where the document will be divided. + Export then produces split-documents.zip containing document - + 1.pdf, document - 2.pdf, and so on. +
++ No. Rotation is stored as a page attribute in 90-degree steps + rather than re-rendering the content, so text, vectors, and + images are untouched. For angles other than 90, 180, or 270 + degrees, use + Rotate by Custom Degrees. +
++ Tick the checkboxes on the pages you want and use Download + selected to get just those pages as selected-pages.pdf. The + workspace stays as it is, so you can keep working and export the + rest later. +
++ The export rebuilds the document page by page, so bookmarks from + the source files aren't carried into the new PDF. Page content, + including text and images, is copied as-is. +
++ No. Page thumbnails are rendered and the final PDF or ZIP is + assembled in your browser, and damaged files are repaired + locally before loading too. Nothing you drop into the grid + leaves your computer. +
+- It chains several PDF operations into one run. Instead of opening a - tool, downloading, and feeding the result into the next tool for - each step, you connect nodes on a canvas, such as PDF Input, - Compress, Watermark, and Download, set each node's options, and - click Run to process everything in sequence. -
-- Yes. The PDF Input node accepts multiple files; a Merge node - combines them into one document, while other nodes process each PDF - separately. When more than one file comes out the end, the Download - node bundles them into a ZIP automatically. -
-- Sockets are typed: PDF (a single document), MultiPDF (several - documents), and Image. A node that expects a single PDF won't accept - a MultiPDF output, so put a Merge node in between, and image outputs - only feed nodes that take images. Connections always run from the - bottom of one node to the top of the next. -
-- Once a PDF is encrypted, later nodes can't read it, so the engine - rejects a workflow where anything other than the output sits after - Encrypt. Move Encrypt to just before Download. Password-protected - inputs are the opposite case: the run pauses and asks for the - password. -
-- The run stops at that node, which turns red with an error message, - and nothing downstream is produced. Fix the setting or the input and - run again; it's easiest to build a two-node version first and add - steps once that works. -
-- Yes. Save stores it as a named template in your browser's local - storage, and Load brings it back in a later session on the same - browser. Export writes the layout to a workflow.json file you can - back up or send to a colleague, and Import restores nodes, - positions, connections, and settings from that file. -
-- No. Templates and exported JSON files hold only the node types, - their settings, positions, and connections; the PDFs are chosen - fresh each time you run. Settings are saved as typed, so avoid - exporting a workflow with a password entered in an Encrypt node if - you plan to share it. -
-- No. Every node runs in your browser with the same engines as the - individual tools, and the only network activity is fetching a - processing module such as Ghostscript the first time a node needs - one. Your PDFs never leave the machine, even in a long multi-step - run. -
-+ It chains several PDF operations into one run. Instead of + opening a tool, downloading, and feeding the result into the + next tool for each step, you connect nodes on a canvas, such as + PDF Input, Compress, Watermark, and Download, set each node's + options, and click Run to process everything in sequence. +
++ Yes. The PDF Input node accepts multiple files; a Merge node + combines them into one document, while other nodes process each + PDF separately. When more than one file comes out the end, the + Download node bundles them into a ZIP automatically. +
++ Sockets are typed: PDF (a single document), MultiPDF (several + documents), and Image. A node that expects a single PDF won't + accept a MultiPDF output, so put a Merge node in between, and + image outputs only feed nodes that take images. Connections + always run from the bottom of one node to the top of the next. +
++ Once a PDF is encrypted, later nodes can't read it, so the + engine rejects a workflow where anything other than the output + sits after Encrypt. Move Encrypt to just before Download. + Password-protected inputs are the opposite case: the run pauses + and asks for the password. +
++ The run stops at that node, which turns red with an error + message, and nothing downstream is produced. Fix the setting or + the input and run again; it's easiest to build a two-node + version first and add steps once that works. +
++ Yes. Save stores it as a named template in your browser's local + storage, and Load brings it back in a later session on the same + browser. Export writes the layout to a workflow.json file you + can back up or send to a colleague, and Import restores nodes, + positions, connections, and settings from that file. +
++ No. Templates and exported JSON files hold only the node types, + their settings, positions, and connections; the PDFs are chosen + fresh each time you run. Settings are saved as typed, so avoid + exporting a workflow with a password entered in an Encrypt node + if you plan to share it. +
++ No. Every node runs in your browser with the same engines as the + individual tools, and the only network activity is fetching a + processing module such as Ghostscript the first time a node + needs one. Your PDFs never leave the machine, even in a long + multi-step run. +
+