PDF zusammenführen

No. WikiPlus PDF Merge is built entirely on the pdf-lib open-source library and runs 100% inside your browser. When you drop PDF files into the merge tool, the browser reads each file's bytes from your local disk into tab memory using the FileReader API. The pdf-lib parser analyzes each document's page tree, resource dictionaries, and content streams without sending a single byte over the network. The merged output is assembled in local memory and delivered to your downloads folder through the browser's native save dialog — the file never passes through a WikiPlus server, a cloud processing queue, or any third-party infrastructure at any point in the workflow. This matters enormously for the documents people most commonly need to merge: signed contracts contain confidential commercial terms; bank statements list account numbers and transaction histories; medical records contain protected health information; tax returns include Social Security numbers, income figures, and financial account details. Uploading any of these to a server-based merger, even one that claims to delete files after 60 minutes, means trusting an opaque retention and security policy you cannot independently audit. With WikiPlus, there is no transmission to trust and no server-side breach surface. You can confirm this yourself: open your browser's developer tools, go to the Network tab, start recording, then run a merge. You will see page assets load on first visit, but no outbound request will carry your file bytes. For maximum assurance with highly sensitive documents, load the page once, then disconnect your internet connection and run the merge. It completes successfully in offline mode because the entire pipeline is local. Tip: keep the original files until you have verified the merged output page count and page order match your expectations.

WikiPlus PDF Merge imposes no file-count limit, no page-count limit, no daily usage quota, and no paywall tier. The only practical ceiling is the amount of free RAM available in your browser tab. The pdf-lib library must hold every source PDF and the partially assembled output in memory simultaneously during the merge operation. On a modern desktop or laptop with 8 GB of RAM and Chrome allocated its default 4 GB tab limit, you can comfortably merge dozens of typical office PDFs in a single operation. Fifty 20-page invoices (totaling 1,000 pages) or ten 200-page reports merge without issue on that hardware class. The scenario that strains browser memory is large collections of scanned documents where every page is stored as a full-resolution JPEG or TIFF bitmap rather than as vector drawing commands. A 50-page scanned report at 300 DPI can exceed 200 MB on disk. Merging ten such files means holding over 2 GB in tab memory simultaneously, which can push the browser toward an out-of-memory condition. When that happens, close other browser tabs, close unused applications to free system RAM, and retry with a smaller subset of files. For very large jobs, split the operation into two batches — merge the first half, download the interim file, then merge that result with the second half. This two-pass approach lets you handle arbitrarily large document sets within the memory constraints of any device. Phones and tablets typically cap browser tab memory at 512 MB to 1 GB, so mobile users should keep batch sizes under ten standard-sized PDFs. Tip: for files with embedded high-resolution images, run them through WikiPlus PDF Compress first to reduce their memory footprint before merging.

No. WikiPlus PDF Merge requires absolutely nothing beyond a modern web browser. There is no account to create, no email address to verify, no credit card to enter, no free-trial countdown timer, and no premium paywall blocking any feature. There is no desktop application to download and install, no browser extension required, and no mobile app needed on iOS or Android. The tool activates the moment the page finishes loading — open the URL, drop your files, and download the merged PDF. That is the complete workflow. WikiPlus PDF Merge works on every modern browser: Chrome, Firefox, Safari, Edge, Brave, Opera, Arc, Vivaldi, and their mobile equivalents on iOS 14+ and Android 8+. The pdf-lib processing library ships as part of the page's static asset bundle, so it runs identically regardless of which browser or operating system you use. Feature parity is complete across all platforms — drag-and-drop reordering, delete-file controls, blank-page insertion between documents, and the download step all work the same on a MacBook, a Windows PC, an iPad, and an Android phone. The tool is permanently free and sustained by non-intrusive display advertising, not by a freemium model that restricts daily usage or adds watermarks to free-tier output. Every merge you run, on every visit, produces a clean PDF with no WikiPlus branding, no added pages, and no embedded metadata attributing the file to this tool. Tip: bookmark the tool URL directly — the static page loads in under two seconds on a broadband connection, making it faster to use than launching any installed desktop PDF application.

No. WikiPlus PDF Merge is a lossless page-concatenation operation, not a re-render or re-encode. The pdf-lib library copies each page's complete content stream, resource dictionary, font references, and image XObjects directly into the output document without passing any data through a rasterizer or image encoder. Every element of every source page — text drawn with embedded fonts, vector paths and bezier curves, full-resolution JPEG and PNG images, ICC color profiles, hyperlinks, AcroForm fields, digital annotations, and rotation metadata — is preserved byte-for-byte in the output. You can zoom to 400% in the merged PDF and it will look identical to the source pages at the same zoom. Text selection, search, copy-paste, and screen-reader accessibility all continue to work exactly as in the originals because the text layer is carried through untouched. The only measurable change in the merged file versus the source files is a modest increase in total document overhead: pdf-lib writes a new cross-reference table and object stream to index the combined document structure, adding roughly 30–60 KB of overhead regardless of page count. This overhead is negligible compared to the content of any realistic document. One caveat: if a source PDF was already corrupt — containing malformed xref tables, truncated object streams, or mismatched byte-length declarations — the merge may fail on that file. Use WikiPlus PDF Repair to fix the source before merging. Tip: after merging, open the output in your default PDF viewer and scroll through every page before archiving or sending — confirming page order takes 30 seconds and prevents the embarrassment of sending a mis-ordered document.

Yes, provided you know the password. When you add an encrypted PDF to the merge queue, WikiPlus detects the encryption flag in the PDF header and displays an inline password prompt for that specific file. You type the password directly in the browser — it is used immediately by pdf-lib to decrypt the file's content streams in local memory and is never transmitted to any server, never stored in local storage or cookies, and never visible in any log. Once decrypted, the file's pages are handled identically to any unencrypted source. The merged output is written without encryption by default, so the combined file opens freely in any PDF reader without requiring a password. If you want the merged output to be password-protected, apply a new password afterward using the WikiPlus PDF Password Protect tool. For PDFs that carry an owner password (a permissions restriction that blocks printing, copying, or editing) but no user-open password, WikiPlus can merge them in most cases because pdf-lib can bypass the permissions flags to read page content — owner restrictions are viewer-level conventions, not encryption of the underlying content stream. If a file has a user-open password you do not know, the content is genuinely encrypted at the byte level and cannot be merged without that password. WikiPlus does not include a password-recovery or brute-force feature — this is intentional, as the tool is designed only to work with documents you are authorized to open. Use WikiPlus PDF Unlock to remove a known password before merging if you want the source files to be permanently unlocked. Tip: remove passwords before a batch merge session to avoid interrupting the workflow mid-queue with multiple password prompts.

Yes, exactly. The order of the file tiles displayed in the WikiPlus PDF Merge interface is the authoritative sequence for the output document. The first tile in the list contributes its pages first; the second tile's pages follow immediately after; each subsequent tile appends its pages in the same sequence. Within each individual input file, pages appear in their original internal order — WikiPlus does not reorder pages within a single source document during the merge. The drag-and-drop reordering system lets you rearrange the file tiles before clicking Merge, and the running page-count indicator at the top of the list updates in real time as you drag files up or down, so you always know the total output page count and the contribution of each file at every position. If you need to reorder pages within one source PDF before merging — for example, moving a signature page from the end to the middle of a contract — use WikiPlus PDF Split to extract that PDF into individual pages, arrange them in a new merge queue, and merge them back into the desired order. Then bring that reordered file into the main merge with your other documents. Each tile also shows a thumbnail of the source file's first page, which helps you visually confirm file identity before committing to the merge — especially useful when working with a queue of similarly sized contract or invoice files. Tip: use the "Add blank page between files" toggle when merging documents that should start on a right-hand (odd-numbered) page in print — this ensures each section begins correctly in double-sided print layouts.

Hyperlinks, AcroForm fields, annotations, and embedded media all survive the WikiPlus PDF merge reliably. The pdf-lib library copies each page with its complete resource dictionary intact, which carries internal cross-document links, external URL annotations, text-input fields, checkboxes, radio buttons, combo boxes, list boxes, and signature widgets. All of these remain interactive in the merged output: clicking a hyperlink still opens the destination, filling a form field still works, and a submission button still triggers its action. Annotations such as highlights, sticky notes, freehand drawings, and rubber-stamp marks are preserved on the page they were placed. Embedded file attachments and multimedia objects (audio, video) that are page-level resources are also retained. Bookmarks — the hierarchical outline tree visible in the Bookmarks panel of Adobe Acrobat Reader — are the notable exception. The current pdf-lib merge implementation concatenates page content streams but does not automatically reconstruct a unified bookmark tree from the individual source documents. Top-level and section-level bookmarks defined in each source PDF are not carried into the combined output's outline structure. For most everyday merge jobs — invoices, receipts, scanned forms, signed contracts, bank statements, email printouts — the absence of a bookmark tree has no practical impact on usability. For long-form documents where navigation depends on bookmarks (legal briefs, technical manuals, academic theses), rebuild the outline after merging using Adobe Acrobat Pro or a dedicated bookmark editor. Tip: test form fields in the merged output by filling and submitting a test copy before distributing the live document — some multi-file merges produce field-name collisions that require manual renaming.

Yes. WikiPlus PDF Merge runs on mobile Safari (iOS 14 and later), Chrome, Firefox, Edge, and Brave on both iOS and Android. The responsive interface scales to any screen size, with touch-optimized controls for file management. Drag-and-drop reordering works on touch screens using a long-press-then-drag gesture: press and hold a file tile until it lifts, then drag it to the desired position in the queue. Tapping the X icon on a tile removes that file from the merge. The practical constraint on mobile devices is memory. Mobile browsers typically cap per-tab memory between 512 MB and 2 GB depending on the device model and OS version. A merge of eight to ten standard office PDFs — contracts, invoices, reports under 10 MB each — completes without difficulty on any phone released in the last four years. A merge of many large scanned PDFs with high-resolution bitmapped pages may exhaust tab memory on lower-end devices. When that happens, close other apps, close all other browser tabs, and retry with a smaller file selection. File access on iOS works through the native Files picker, which exposes iCloud Drive, local On My iPhone storage, Dropbox, Google Drive, and any other installed file-provider app. On Android, the standard file picker provides access to Downloads, Google Drive, and any provider registered with the system's Storage Access Framework. The merged PDF downloads through the browser's standard download mechanism and appears in your Downloads folder or, on iOS, can be shared directly to Files, Mail, or any other share-sheet destination. Tip: for very large merges on mobile, switch to a desktop or laptop — browser memory limits on phones are real and cannot be circumvented by any workaround.

WikiPlus PDF Merge is architecturally aligned with the data-minimization requirements of GDPR Article 5(1)(c) and the technical safeguard principles of HIPAA's Security Rule because the tool never collects, processes, transmits, or retains any content from your PDF files. All processing is 100% client-side: the pdf-lib library runs as compiled JavaScript inside your browser tab, and no personally identifiable information (PII), protected health information (PHI), financial data, or any other content from your documents ever reaches a WikiPlus server, a cloud processing API, a CDN edge node, or any third-party analytics pipeline. There is no server-side breach surface for file content because there is no server involved in the file-processing path. WikiPlus is not itself a HIPAA-covered entity and does not offer Business Associate Agreements (BAAs), because a BAA is only required when a vendor has access to PHI — and WikiPlus has zero access to your document content by design. The same structural argument applies to GDPR: no processing of personal data by the data processor (WikiPlus) occurs, so the Article 28 processor agreement requirement is not triggered for file content. Your organization's legal or compliance team can verify these claims independently: the pdf-lib library is open source (MIT license) on GitHub; the WikiPlus merge page ships with a Content-Security-Policy header that blocks form submissions and cross-origin fetches; and you or a security engineer can confirm the absence of file-data transmission by monitoring the browser's Network panel during a merge. For regulated environments requiring written documentation, the open-source code itself serves as the attestation. Tip: for maximum assurance with highly sensitive documents, use the tool in offline mode — load the page, disconnect from the internet, run the merge, reconnect only after downloading the output.