跳到主内容
MoGuan

PDF a Word

Convierte tus documentos PDF en archivos Word editables.

Click to select or drop a PDF here

Processed entirely in your browser — never uploaded

A PDF doesn't store paragraphs. It stores 'draw this glyph at this coordinate.' So converting a PDF to Word is never restoration — it's reconstruction, guessing the structure back out of scattered characters.

There are two ways to guess here. Structure extraction reads font sizes to infer heading levels and builds an editable .docx right in your browser; the file never leaves it. AI reflow sends only the text extracted locally to DeepSeek, which reorganizes it into clean paragraphs, lists, and tables before the .docx is generated — your original PDF is never uploaded.

Neither mode recreates the original layout or keeps image styling. You get editable text, not a pixel-perfect copy. Scanned PDFs need OCR first; with no extractable text on the page, you'll get an empty document.

Free, unlimited conversions, 50MB per file. Pro raises that to 100MB.

FAQ

Why doesn't the converted Word file match my original PDF's layout?

It isn't a bug — it's the boundary of the feature. I won't promise 100% fidelity. Both modes rebuild text and heading levels only; neither recreates the original layout or preserves image styling. And if Word doesn't have the font your PDF used, it substitutes a lookalike — character widths change, so line breaks and page counts move. For anything that matters (a contract, a bid, a report going to a client), open the .docx in whatever software you'll actually deliver from and check it before you send.

What's the difference between Structure Extraction and AI Reflow when converting PDF to Word?

Structure extraction runs entirely in your browser: it reads font sizes to infer heading levels and writes the .docx locally, so the file never leaves the tab. Good for tidy documents — reports, papers, specs. AI reflow sends the locally extracted plain text to DeepSeek, which reorganizes it into clean paragraphs, lists, and tables. Good for PDFs with broken line wrapping, two-column layouts, or TOC page numbers bleeding into the body. The tradeoff: the text leaves your machine, and it's 5 free runs a day. Try structure extraction first; switch if it disappoints.

Does converting a PDF to Word upload my file to a server?

Structure extraction doesn't — pdf.js and the .docx builder both run in your browser's memory, and the tool works with the network off. AI reflow doesn't upload the PDF either; only the plain text already extracted locally goes out, and it goes to DeepSeek, which the UI names plainly: 'DeepSeek · 5 free per day'. If even the text can't leave — an unannounced acquisition memo, say — stay on structure extraction. As with the other tools on this site, you can verify the network behavior yourself.

Can I convert a scanned PDF to an editable Word document?

Not directly. A scanned PDF is a stack of images with no text layer to extract, so both modes will hand you an empty document or a few stray characters. Run it through OCR first to produce a PDF with a real text layer, then convert that. Contracts photographed on a phone and old archive scans are usually this kind of file. Quick test: open the PDF and try to select a sentence with your cursor. If you can't, it's a scan.

How many PDFs can I convert to Word for free, and what's the file size limit?

Conversions are unlimited — there's no daily count. The cap is per file: 50MB free, 100MB on Pro. Why those numbers: conversion happens in browser memory, and pdf-lib's peak usage runs roughly 3-5× the file size. 100MB is the ceiling that still held up in my testing; 50MB is a conservative margin for lower-spec machines. Limits differ across tools on this site — some raise on Pro, some can't, because the underlying engine caps out at 50MB regardless of what you pay.