Use PDFSanitize in Virtual Machines

Applies to: Enterprise

Edition requirement

Virtual-machines are supported in the Enterprise edition. Standard and Pro are licensed for eligible physical, non-server Windows systems.

Document scope in a VM

PDFSanitize processes files visible to the Windows guest through its file-system paths. It does not sanitize hypervisor snapshots, host-level backups, replicated storage, cloud synchronization history, or copies that exist outside the guest simply because a file inside the guest was sanitized.

Storage behavior

Sanitized outputs are written beside the source PDFs from the guest’s perspective. For virtual disks, mapped drives, and redirected shares, confirm where those files physically reside and whether snapshot or backup systems preserve the original source.

Licensing and cloned VMs

Paid licensing uses a device identity stored locally for the product. Cloning, reimaging, or restoring virtual machines can affect how activations are represented. Use an Enterprise deployment procedure that accounts for license transfer and avoids uncontrolled duplication of activated images.

Operational validation

Before production use in a VM, test:

  • Folder import and file permissions;
  • Large-PDF rendering performance;
  • Temporary storage capacity;
  • Licensing connectivity;
  • Report and certificate output paths;
  • The relationship between guest files and host-side backup or snapshot retention.