Hello,
the new version 7.0.1 of PDFsam Visual is out. This is a major update with two new tools, a refreshed engine and a long list of fixes.
Clean PDF pages and edit metadata
We added Clean PDF, a new task that removes metadata, XMP metadata and annotations from your PDF files in bulk. It’s a quick way to strip out information you don’t want to share before sending a document out.
Alongside it, a new Edit metadata task lets you modify a document’s properties, such as title and author, directly from the app.
The new version 4.1.1 of PDFsam Visual has been released. We upgraded Electron and the PDF engine and the render engine to their latest version. All the upgraded versions contain a number of bug fixes, security fixes and improvements.
You can download it from the Download page.
Enjoy
Hello,
the new PDFsam Basic 4.3.3 is out. We upgraded the bundled JDK using the latest 11.0.16, the PDF engine to include some fixes and we improved the loading of csv files containing the input list.
You can download it from the download section.
Enjoy
Hello,
we released the new version of PDFsam Basic where we upgraded translations and PDF engine.
We improved the handling of broken PDF files where the PDF engine has to perform a full scan of the PDF objects and we now handle correctly those files containing garbage bytes at the beginning.
As usual you can download it from the download section.
Enjoy
We released the new version 4.0.2 of PDFsam Visual. PDF engine and render engine have been updated. An issue affecting the Resize tool and the Merge tool when the Normalize checkbox was active has been fixed. Tiling patterns streams are now properly processed. You can download it from the Download page.
Enjoy
Hello,
we just released the new version 4.3.0 of PDFsam Basic. We upgraded translations, bundled JDK and Sejda to their more recent versions. A number of fixes were added to Sejda but most notably we fixed:
An issue with the Normalize page size in the Merge tool where outline and link annotation destinations may end up with wrong destination coordinates
An issue with Tiling patterns streams that weren’t processed during the optimization process. This could lead to missing pattern resources in some cases