How to Merge PDF Files in the Correct Order: Step-by-Step Guide | GoToolstack
Learn how to combine multiple PDF documents into a single file with exact page sequence. Tested with synthetic files, explains browser-side memory and format limits.
Encrypt PDF documents with strong AES passwords to prevent unauthorized access and printing.
Client-Side PDF Protection Suite applies standard cryptographically secure encryption to PDF documents and unlocks password-protected files directly inside the browser environment powered by QPDF compiled to WebAssembly (WASM). Operating directly upon raw PDF byte streams inside an in-memory virtual filesystem (MEMFS), it configures standard PDF security handlers (Standard Security Handler R=4 for 128-bit AES and R=6 for 256-bit AES), encryption dictionaries, and permission bitmasks without external server round-trips.
The interface is organized into two core workflows: 'Lock PDF' and 'Unlock PDF'. In encryption mode, users configure separate User Passwords (required to open and view the document) and Owner Passwords (required to modify document permissions and restrictions). An interactive permissions matrix passes granular flags to the QPDF WASM engine to restrict text and image copying (--extract=n), disable printing (--print=none), or lock document modification (--modify=none). Users can select between industry-standard 256-bit AES (Acrobat 9.0+) and 128-bit AES (broad compatibility, Acrobat 7.0+) encryption standards. A dynamic password strength meter provides real-time entropy feedback.
Concrete Scenario: A human resources director prepares an executive compensation agreement (PDF, 2.4 MB) containing sensitive salary figures. In the Lock tab, setting an 18-character User Password, configuring an administrative Owner Password, and enabling 'Prevent text and image copying' executes the sandboxed QPDF WASM engine locally in memory, generating an industry-standard 256-bit AES-encrypted PDF that restricts unauthorized recipients from viewing or copying text without the correct passphrases.
Both encryption key derivation, permission dictionary serialization, and decryption verification execute exclusively in local browser memory via QPDF WebAssembly. Sensitive passwords, master cryptographic keys, and unencrypted document buffers are processed locally in your browser and are not transmitted to GoToolstack servers.