What does this slide merger do?
Use this tool to combine two or more local .pptx presentations into one merged .pptx file. It works with individual slides, so you can choose slides from each file and set their final order in the browser.
Choose slides with per-file ranges
Each file has a Slide range field. Slide numbers start at 1 and follow that file's own order. The default value is all. To select specific slides, use a value such as 1-3,5,8-10. Invalid items appear as ignored in the range status. Changing a range rebuilds that file's entries around its first existing position, so an existing interleaved order can change.
Reorder or remove slides
The Slides in this merge (drag to reorder) list contains all selected slides from every file. Drag a slide anywhere in the combined list. Use its Remove slide control to leave it out. Removing a source file also removes its selected slides from this list.
What the merge copies
Slides are copied as PPTX/XML package parts rather than rasterized images. When referenced parts are available, the merge copies layouts, masters, themes, media, notes, charts, SmartArt, embedded workbooks, and OLE objects with the slide. Linked external targets remain links; the linked files are not bundled. OLE objects are copied as-is and may not be editable in all viewers. Missing referenced parts can be reported, and a slide may be skipped if its root part cannot be copied.
Review preflight findings before merging
After you add files, review Conflicts detected (before export) when it appears. This preflight scan checks every added file, including slides you later leave out. Findings can cover theme differences, linked external media or objects, embedded VBA projects, embedded fonts, and chart, SmartArt, or embedded-object data.
- Different themes may make the overall design look inconsistent.
- Embedded fonts are not carried into the merged file, so text may render differently on a machine without those fonts installed.
- Complex chart or SmartArt data may need PowerPoint to re-render if you edit it later.
Understand the final merge report
After processing, the result area shows a Merge report with slide and source counts. Its table uses Level, Source, and Detail columns. Entries can be warning, info, or blocked. The final report can identify missing referenced parts, guessed content types, OLE objects that may not be editable in all viewers, and slides that could not be copied and were skipped. It is not a re-check of every preflight category for every included slide.
How to merge presentations
- Add two or more .pptx files through the drop area or browse files.
- Adjust each file's Slide range if needed.
- Review Conflicts detected (before export) when it appears.
- Drag slides in Slides in this merge (drag to reorder) and remove unwanted slides.
- After the files and ranges are ready, merging starts automatically.
- Review Merge report, then use Download merged file. The generated filename is
merged-presentation.pptx.
Formats, limits, and local processing
The input workflow accepts only .pptx. Files ending in .ppt, .pptm, DOCX, ZIP, PDF, or another extension are rejected. An accepted .pptx package may contain an embedded VBA project; it can be flagged, but macros do not run in the browser.
You can add up to 20 files with a combined size of approximately 250 MB. The implementation does not define a separate maximum slide count. Files are read and merged locally in the browser, and the original files are not modified.
Frequently asked questions
Does merging flatten my slides to images?
No. Slides are copied as PPTX parts, not rasterized images. The implementation does not guarantee that every object remains editable in every viewer.
What happens if my source files use different themes?
Each file's slides keep their own theme, layouts, and master - they are not converted onto a shared theme. If source themes differ, this is flagged in the conflict report before you export, so you know the merged deck may look visually inconsistent across sections.
Are linked (non-embedded) media and macros handled?
Linked media or objects remain external references and the linked files are not bundled. An accepted .pptx may contain an embedded VBA project; it can be flagged, but it will not execute in the browser. A .pptm file itself is rejected because the input accepts only .pptx.
Does it upload my files anywhere?
No. Files are read and merged entirely in your browser using JSZip and the File API. Nothing is sent to a server, and your original source files are never modified.