Merge is not available
This planned page does not combine documents. The control below does not run a merge.
Client-side · zero upload · OpenXML
Saving a file needs JavaScript. The explanation below is in the page HTML.
This planned page does not combine documents. The control below does not run a merge.
No merge drop. Adding a file here does not upload it and does not merge it.
| Topic | This browser | Server upload | By hand |
|---|---|---|---|
| Status | Not currently available. The view is mounted so the plan is visible. | No package is uploaded by this page. | You can still combine documents in Word yourself. |
| Batch size | Not published. The missing tool is not described as unlimited. | No upload quota is stated for a tool that does not run. | Word's document size is outside this page. |
| Future package | A later design would remap word/_rels/document.xml.rels and could hash identical word/media bytes. | A server merge would need the files first. This page does not send them. | Copying between open documents does not use this page. |
| Charts and styles | Not every chart is under word/media. Style and table conflicts would not be promised lossless. | A remote merge could also change styles. | Word resolves conflicts with its own rules. |
| Today | The button records that nothing was processed. | Nothing is transmitted. | Use Word if you need a merge now. |
How this page works
Read the planned status
Merge is not currently available. This route is not the splitter wearing a different title.
Do not expect a result
Choosing a file or clicking the button does not build a merged .docx and does not upload anything.
Use the splitter for a real task
The splitter page can divide one .docx locally. It does not merge files.
Under the hood
A merger is not currently available. This is a later design, not a function you can run, and nothing is uploaded. A future local JavaScript tool, not WebAssembly, would append word/document.xml bodies in a chosen order. It would remap ids in word/_rels/document.xml.rels so styles, headers, and pictures do not collide. Identical word/media bytes could be kept once by a content hash. That hash would miss a chart stored in its own chart part rather than word/media. [Content_Types].xml would list every remaining part. Basic styles and whole tables could be carried over, but the same style id can differ between files, so conflicts would not be lossless. Numbering, fields, and section breaks could change. No batch-size limit is published, because the tool does not exist, and the page does not call the missing tool unlimited. The 100 MB compressed and 250 MB expanded limits belong only to the splitter that already runs.
Questions
Can I merge files here?
No. Merge is planned and not currently available. The button does not produce a document.
Would a future merge be lossless?
No such promise is made. Remapping relationship ids and keeping basic styles and tables would still leave style conflicts and some chart parts unresolved.
Are charts just files in word/media?
No. Some pictures live under word/media. A chart can live in a chart part referenced from the document, so a media hash would not cover every chart.
Is there a batch limit?
None is published, because the merger does not run. That is not a claim of unlimited files.