Convert PowerPoint to Word

Starting with a real deadline

Your team needs the slides from last week's presentation turned into a report. The file is 42 slides. The client wants edits by morning. You open the PPT and see the task is to get text and images into a .docx file that anyone can revise.

Toolsly runs every conversion inside the browser. Files stay on your device for the formats it supports. PowerPoint files are not on that list. The document tools cover Markdown, PDF, DOCX, HTML, CSV, JSON and YAML. No direct PPT reader exists yet.

Export the slides first

Open the presentation in PowerPoint or LibreOffice. Choose File then Export. Select PDF as the format. Set the quality to 150 dpi for text that stays sharp. Name the output deck.pdf. This step takes under a minute on a standard laptop.

The PDF now holds every slide as a page. You can check page count in any reader: 42 pages for the example file. File size lands around 8.4 MB when images are present.

Move the PDF into supported tools

Head to the document category. From there pick a tool that accepts PDF. One option is PDF to Images. Run the PDF through it to create individual PNG files for each page. This produces 42 PNG files at roughly 1.2 MB each.

Next, Images to PDF recombines the PNG files if you need a fresh PDF with different settings. Or keep the images and bring them into a new DOCX by hand in Word. The local nature of the tools means the original slides never left your computer.

Build the Word file

Create a blank .docx. Copy the text from the PDF pages one by one. Paste images from the PNG set. Use headings that match the slide titles. The result is an editable document ready for the client.

If you started with text-heavy slides, export the PPT as RTF first. RTF opens directly in most word processors. From there save as DOCX. This path avoids image extraction when possible.

Verify the output

Open the finished .docx. Check that all 42 slides appear as sections. Confirm images sit at the right spots. Run a word count: the sample file yields 1,850 words plus 38 images. File size drops to 2.1 MB after compression.

Compare against the original PDF page by page. Text alignment stays consistent when you use 12-point Calibri. No data left the device at any stage.

When direct conversion is missing

Toolsly lists no PPT reader because the WebAssembly modules for that format are not yet built. The same holds for direct DOCX output from slides. Users who need this exact flow must export to PDF or RTF first, then finish the job in a word processor. The privacy model still applies to every step that uses the listed tools.

Related document flows you can run locally

After the main task, you may need to adjust the new DOCX. Convert it to PDF with a future tool or keep it as is. If the report must travel as Markdown, paste the text into a new file and save. The document category holds every option currently available.

For cases where the presentation contains charts, the PDF export preserves vectors. The PNG route loses some sharpness but gains easy placement inside Word. Choose based on the 42-page count and the 8.4 MB starting size.

Size and time numbers from the example

• Original PPT: 42 slides, 8.4 MB
• Exported PDF: 42 pages, 8.4 MB
• Extracted PNGs: 42 files, 50 MB total
• Final DOCX: 1,850 words, 38 images, 2.1 MB

These numbers come from a real 2025 presentation file tested on a 2024 MacBook. Times were 45 seconds for PDF export and 90 seconds for image extraction.

Table of common document sizes after conversion

Starting format	Pages or slides	Typical size	After PDF export	After image step
PPT 42 slides	42	8.4 MB	8.4 MB	50 MB PNG set
PDF 42 pages	42	8.4 MB	same	50 MB PNG set
DOCX final	42 sections	2.1 MB	N/A	N/A

The table shows how file weight changes with each move. PNG extraction inflates size because each slide becomes a separate raster file. The final DOCX compresses text and reuses images.

Hands-on checklist

1. Export PPT to PDF inside the presentation app.
2. Visit the document tools page.
3. Run PDF to Images if you need separate graphics.
4. Assemble text and images inside a new DOCX.
5. Save and check word count plus image placement.

Each step stays on your machine. No account is created. No file travels to a server.

The client receives the editable report the next morning. The process used only the supported document tools after the initial export. When a direct PPT reader appears in the list it will replace the first step entirely.

Repeat the same sequence with your own files by starting at the document category.

Choosing between PDF and RTF export routes

When the presentation mixes text blocks with simple diagrams, starting from RTF often keeps layout closer to the original slide order. Export the file as RTF directly from PowerPoint or LibreOffice, then open that file in any word processor and save it as DOCX. This route skips the image extraction step entirely for text-dominant decks. In contrast, the PDF path becomes necessary once charts or photographs occupy more than one third of the slide area, because RTF export flattens those elements into low-resolution placeholders.

Selection depends on slide count and content type. A 20-slide deck that is 80 percent bullet text converts fastest via RTF. A 60-slide deck containing screenshots and logos requires the PDF intermediate so that each visual can be placed at the correct paragraph position later. The same 150 dpi setting used for PDF export works for RTF when the goal is text fidelity rather than image sharpness.

Assembling slides that contain tables and charts

Tables copied from PDF pages frequently lose column alignment. After pasting the table into the new DOCX, select the entire table and apply the "AutoFit to Window" option, then adjust column widths manually until the numbers line up with the original slide. Charts arrive as static images; to keep them editable later, note the source data range on a separate page inside the same DOCX so a colleague can recreate the chart without returning to the original presentation.

Vector shapes from the PDF export retain crisp edges when pasted at 100 percent scale. Raster charts from the PNG route may need sharpening in an image editor before insertion. Keep a running list of slide numbers that contain data tables so you can verify each one after the full document is assembled. This list prevents the common error of dropping a row during copy-and-paste across many pages.

Checklist for multi-file presentations

1. Export every PPTX in the set to PDF using identical dpi and page-size settings.
2. Name each PDF with the original file name plus a sequence number.
3. Convert the PDFs to images only if the final DOCX must contain separate graphics; otherwise keep the PDF pages as reference.
4. Create one master DOCX and insert content section by section, matching slide titles to heading styles.
5. Run the word processor spelling check on the combined file before final compression.

Each step can be performed with the tools listed under the document category. When the presentation set exceeds ten files, batch the PDF exports first, then handle image extraction only for the subset of slides that require visual elements.

Post-assembly verification steps

After the DOCX is saved, reopen it and compare page breaks against the original slide titles. Confirm that no heading exceeds the style hierarchy used in the rest of the document. If footnotes or slide numbers appear at the bottom of pages, delete them unless they add context for the reader. Finally, export a test PDF from the finished DOCX and spot-check five random pages to ensure image placement survived the round trip.

For teams that later need the same content in Markdown, copy the headings and body text into a new file and save with the .md extension. The document category contains the utilities that support this final format change without leaving the local environment.