1 つの Word ドキュメント。連続したページ番号。自動ブックマーク。完了。

Yes — the merge happens on our backend so we can run the chapter-bookmark generation and TOC update reliably (browser-only Word libraries can't reproduce these). Files are encrypted in transit (TLS 1.3), processed on a hardened cloud worker, and auto-deleted after one hour. We never log file contents and never share data with third parties. Audit-grade compliance for legal and financial workflows.

Because iLovePDF treats Word as a side-effect of its PDF pipeline — it converts your .docx to PDF, merges the PDFs, then converts back. The bookmark layer doesn't survive that round-trip. ExcelMaster.ai stays in the Word OOXML format end-to-end so bookmarks, fields, comments, and tracked changes all preserve.

It forces every appended chapter to use the FIRST document's style table — so Heading 1 looks the same throughout, Normal is the same paragraph spacing, the title page font is consistent, etc. Use it when you have a unified template (thesis, brand-guideline doc, multi-author novel). Don't use it when each source's formatting is intentional (legal contracts where each contract's font conveys meaning).

Two reasons. (1) The source documents don't use Heading 1/2/3 styles — Word's TOC field sniffs heading styles to build entries. Apply Heading 1 to your chapter titles before merging. (2) UpdateFields didn't run; this shouldn't happen with our pipeline (we always call UpdateFields on save), but if you saved over the file in Word, hit Ctrl+A → F9 to refresh the field.

Yes. We accept .doc, .docx, .rtf, .odt, .dotx, .docm, and .dotm. The output defaults to .docx (modern Word format) but you can pick .doc or .rtf if your downstream tool needs legacy compatibility.

Drop them in like any other file. Our backend detects the encrypted-document signal, returns a 'needs_password' response, and the frontend pops a password modal asking only for that file's password. We never brute-force, never store the password, never log it. Cancel the modal and we won't include that file in the merge.

Yes. Tracked changes and comments are part of the OOXML revision history; AppendDocument carries them across with their author + timestamp metadata intact. If you want to merge a clean copy, accept all changes in each source first (Review tab → Accept All in Document).

Each source brings its own headers and footers, attached to its section. The merged document keeps them as separate sections so chapter-specific headers (e.g. 'Chapter 1 — Introduction') stay where they belong. Page numbers run continuously across sections (when force_continuous_pages is on, default).

Yes — use the up/down arrows next to each file. Top of the list becomes chapter 1, bottom becomes the last chapter. Reorder any time before clicking Merge.

It's a memory ceiling — each Word document loads into a parsed OOXML tree and large multi-doc merges stack in memory. 50 × 100 MB covers thesis chapters, multi-volume contracts, and novel manuscripts. If you need more, split your merge into two batches and merge the results.

It's really free. No signup, no watermark, no daily cap, no paywall after N merges. We pay for our infrastructure with a paid VSTO add-in that runs Excel automation tasks for power users — the free tools are a way to introduce the brand. We don't sell your data; we don't run ads.

Manual: open document 1, Insert → Object → Text from File for each subsequent doc, then walk through every section adjusting page numbers, bookmarks, headers — typically 10–20 minutes for five chapters. Our merger does it in under 30 seconds. Same output, drastic time savings.