About PDF to Word Converter
A PDF holds glyphs at coordinates, not paragraphs, so a converter has to work out what the geometry means: which lines belong to one paragraph, where a column ends, which rules make a table, and which cluster of drawing is a chart rather than a border. This one shows that reading before you download it — every heading, table and picture it found, laid out as Word will lay them out — because the failure worth catching is the silent one, a lost column or a chart that became a row of stray axis labels.
Conversion happens in three passes, and the page names each one as it goes because each fails differently. The first reads every page with Mozilla's pdf.js, the same engine Firefox uses to display PDFs, collecting each run of characters with its position, its size and the font it was set in. The second decides what that arrangement means. The third crops the pictures and writes the .docx, which is a ZIP of XML parts assembled here rather than by an office suite.
The middle pass is the one that decides whether the result is worth having. Text on a facing page arrives in whatever order the producer emitted it, so runs are sorted by baseline and rebuilt into lines; lines are joined into paragraphs using the leading, the indent and whether the line before stopped short of the margin; a word split across a line break has its hyphen removed and is closed up again. Two columns are separated before any of that happens, by finding the vertical band of white that no line crosses — build the lines first and the left column's words are welded to the right column's, and nothing later can undo it.
Formatting survives at the level that matters for editing. A line set larger than the body becomes a Heading 1, 2 or 3, so the navigation pane in Word fills in and the document can be restructured rather than retyped. Bold and italic are kept run by run, from the PostScript name of the font rather than from guesswork. The families themselves are swapped for metric-compatible ones — Arial where the PDF used Helvetica, Times New Roman where it used Times — because those substitutes have identical character widths, so a line that filled its measure still fills it instead of reflowing and pushing a page of text downwards.
Tables and lists come back as tables and lists. Where a table was drawn with ruling lines, the grid is read from the lines themselves and the words are posted into cells, which is the case worth trusting: the producer has said where the cells are. The header row is marked as one, so it repeats if the table breaks across pages in Word. A bullet or a number at the start of an item becomes Word's own list numbering rather than a character in the text, which is why the bullets stay aligned when the list is edited. Tables ruled by nothing but alignment are found too, but only when you ask, because a hanging indent looks exactly like a two-column table to a computer and a wrong table is harder to fix than a missing one.
Charts, diagrams and photographs are the part most converters quietly drop. A chart is not an object inside a PDF: it is several hundred separate paths and thirty scraps of text, which is why a naive conversion produces a paragraph reading "0 100 200 300 Q1 Q2 Q3 Q4" and no chart. Here the drawing is grouped by proximity into one picture, the labels standing inside it are taken out of the running text and kept with it, a numbered caption underneath is recognised and placed as a caption, and the whole region is redrawn as an image at a resolution taken from the file's own pixels. Photographs come out at their own density rather than at a guess.
What the tool will not do is pretend. A PDF made by scanning paper contains pictures of words and no text at all; no rearrangement of geometry can recover them, and the verdict panel says so instead of handing back an empty document. A file whose fonts lack the table that maps glyphs back to characters produces mojibake, and that is reported as a percentage rather than shipped quietly. Text colour, footnotes, equations and form fields are not carried across yet. The aim is a document whose words, structure and pictures are correct and editable — not a pixel-perfect impersonation of the original, which is what the PDF itself already is.
Common use cases
- Editing a report that arrived as a PDF when the original document is long gone.
- Lifting the tables out of a research paper or an annual report to work on the numbers.
- Reusing the text of a contract or a policy as the basis for a new version.
- Getting a CV back into an editable state after it has been through a PDF export.
- Rebuilding a presentation handout or a newsletter whose source files were never kept.
- Pulling the charts out of a report as pictures for a deck, with their captions intact.