---
title: "PDF to Word Converter - PDF to DOCX Online Free - CartHacker"
description: "Turn a PDF into an editable Word document. Rebuilds paragraphs, headings and lists from the text layer, in your browser, with no upload."
url: "https://carthacker.com/pdf-tools/pdf-to-word/"
image: "https://carthacker.com/wp-content/themes/carthacker-core/assets/og/pdf-pdf-to-word.jpg?v=1791719545"
publisher: "CartHacker (carthacker.com)"
language: "en"
---

# PDF to Word Converter: Get an editable document back, without sending the PDF anywhere

Drop your PDF into the emerald zone below and get a Word file back. **Paragraphs are rebuilt from the glyph positions, headings from the type size, and lists from their markers, so you get a document you can type into.** It works from the text layer the PDF already carries rather than reading letterforms off a picture, so a scanned document with no text layer in it cannot come back editable, and this page says so before it hands you a file. Everything runs on your own processor. Nothing is uploaded, which matters because this is the direction people use for contracts, invoices and tenancy agreements.

- Files never leave your device
- No installation, no watermark
- Works offline once the page is open

PDF to DOCX, Live

- **Privacy:** 100% private
- **Your plan:** Free to use
- **You get:** DOCX

Your files are read by JavaScript running on your own machine. There is no upload, no queue, and no copy on our server to delete later.

The converter above is ready now. **The guide below explains why this direction is genuinely hard** - a PDF contains no paragraphs, no words and no reading order, only glyphs at coordinates - and exactly how those are turned back into a structured document, what that reconstruction gets right, and how to tell in advance whether your file will work.

## How to Convert a PDF to an Editable Word Document

Two minutes, nothing to install, no account for your first run. This **PDF to Word converter** executes inside the page you are reading, so every step below happens on your machine.

1. **Drop your PDF into the emerald zone.** Click the drop zone above or drag the file anywhere onto this page. Each PDF is parsed as it lands, and the card that appears shows its page count with a preview of page one, so you can confirm you picked the right file before converting anything. Nothing is transmitted at any point.
2. **Choose editable text or pages as pictures.** Editable text is the default, and it rebuilds real paragraphs, headings and lists out of the text layer the PDF already carries. Pages as pictures places each page into the document as a full-page image instead, which is the only sensible answer for a scan, because a scan holds pixels rather than characters and there is nothing inside it to rebuild.
3. **Decide about headings and page breaks.** Detect headings promotes lines set noticeably larger than the body to Heading 1, 2 or 3, which makes the navigation pane in Word work. Keep a page break at each page is off by default so the text reflows as a continuous document, which is what you want if you are going to edit it.
4. **Convert, then fix the structure before the words.** Press Convert to Word and the work happens on your processor. Open the result and work top down, checking the headings first, then any list, then the body, because a structural mistake caught early saves you from reading the same page three times over. Structural corrections take two minutes. Retyping does not.

Dropping several PDFs converts them in sequence into one document. If you want them separate, run them separately.

## The Engineering Behind PDF to Word Conversion

Converting Word to PDF is a format conversion. Converting PDF to Word is an inference problem, and understanding why is the difference between using this tool well and being annoyed by it.

**A PDF contains no paragraphs.** It contains no words, no sentences, no lists, no headings and no reading order. What it contains is a stream of instructions that say, in effect: select this font at this size, move to this coordinate, paint these glyphs. Everything a human reads as structure, whether that is a paragraph, a bullet or a heading, is an artifact of where the glyphs happened to land on the page, and your eye supplies it rather than the file recording it.

In the machine's view, the document you are holding is a scatter plot of characters. Rebuilding a Word file out of it means inferring every structural fact back from geometry, which is a chain of seven decisions where an early wrong answer propagates into everything after it. Here is the order it happens in:

1. **Read the glyph runs.** Every fragment of text on the page, with its transformation matrix, which yields its position and its rendered size, plus the internal name of its font.
2. **Flip the coordinate system.** PDF measures upward from the bottom left corner of the page, while reading order runs downward from the top, so every coordinate has to cross that boundary exactly once. Cross it twice and the document comes back inverted. Miss it and page one begins at the footer.
3. **Group fragments into lines.** Fragments sharing a baseline belong to one line, with a tolerance proportional to the type size rather than a fixed one, because a fixed tolerance either merges two lines of 8 point footnotes or splits a line of 30 point display type that happens to contain a superscript.
4. **Reinsert the spaces.** This surprises people: PDF producers frequently emit "Total" and "Revenue" as two runs with no space character between them at all. The gap between them is the only evidence a space was ever there, so a gap wider than about a fifth of an em becomes a space, and a much wider gap is recorded as a possible column boundary.
5. **Group lines into paragraphs.** Three signals, in order of reliability: a vertical gap noticeably larger than the running line pitch, a previous line that stopped short of its block's right margin and therefore ended something, and a change of left indentation.
6. **Detect headings and lists.** A line set noticeably larger than the median body size becomes a heading, ranked into level one, two or three by how large that ratio is. A line that opens with a bullet character or a numbering pattern becomes a list item, and the marker itself is stripped out, so Word does not print its own bullet next to the one carried over from the PDF.
7. **Write the DOCX.** Real WordprocessingML, with a style sheet, numbering definitions, and paragraphs carrying proper heading styles.

### The detail that most converters get wrong

The short line signal is the most useful paragraph break indicator there is, and it is worthless if the right margin is measured across the whole page. One table whose last column runs far to the right would declare every line of an ordinary paragraph short, and the page comes out as one paragraph per line, which is the classic broken PDF to Word result everybody has seen.

So lines are grouped by where they start and what size they are set in, which is a good proxy for belonging to the same block, and **each block carries its own right margin**. That single change is the difference between a document you edit and a document you retype.

**Verify the privacy claim in thirty seconds.** Load this page, disconnect from the internet completely, then convert a PDF. It still works, because there is no server-side step for it to depend on, and no converter that uploads your file could survive the same test.

## Scanned PDFs: Why They Come Back Empty, and What To Do

This is the single most common disappointment with any **PDF to DOCX converter**, and the reason sits in the file rather than in the software. Learn the difference now and you will never be surprised by it again.

There are two completely different things people call a PDF:

- **A born-digital PDF.** Exported straight from Word, InDesign, a browser, an accounting system or a shop platform. It carries a text layer, meaning real characters with real coordinates and a real font name attached to every one of them, which is exactly the raw material this converter reads. Try to select a sentence with your mouse and it highlights. These convert well.
- **A scanned PDF.** Produced by a scanner, a photocopier or a phone camera app. It is a photograph of a page wrapped in a PDF container, and there are no characters inside it at all, only pixels arranged so that a human eye reads them as letters. Selecting text does nothing. **A file like this cannot come back as editable text**, here or in any converter that does not run optical character recognition over it first.

A converter that silently produces an empty Word file from a scan is doing the worst possible thing, because the user believes it worked and discovers otherwise later. This one checks: **if the text layer holds essentially nothing, the conversion stops and says so in plain words**, and names the two things that actually help.

### The thirty second test

Open the PDF and try to select a single sentence with your mouse. If individual words highlight as you drag across them, there is a real text layer underneath and this converter has genuine characters to work with rather than a picture of them. If nothing highlights at all, or the entire page highlights as one solid block the moment you click, it is a scan. Do that before you convert. The test costs nothing and it is right every time.

### What to do with a scan

1. **Switch to Pages as pictures.** Each page becomes a full-page image inside a Word document, at whichever of the four resolutions you pick, from 96 up to 300 dots per inch, with the Word page sized to match the PDF page so that nothing is cropped at the edges. You cannot edit the text, but you get a .docx you can annotate, add pages to, and file with the rest of your documents. For a signed contract you only need to countersign, this is often exactly enough.
2. **Or run optical character recognition first.** That reads the letterforms off the picture, decides which character each shape is, and welds a real text layer onto the PDF underneath the image you can already see. Convert the searchable PDF it produces and you get genuinely editable text out of this page.

There is a third case. Some PDFs carry a text layer that exists but is wrong, usually because optical character recognition was run at low quality or over a scan that went through the feeder crooked. Those convert to a Word document full of plausible-looking nonsense: real words, in real paragraphs, that are not the words printed on the page. If your result reads like a bad transcription rather than like your own document, that is the cause, and re-running the recognition at higher quality on a straightened scan is the fix.

## What Comes Back, Stated Precisely

Every honest answer here is a probability rather than a guarantee, because the whole process is inference. What follows is what actually happens on real documents.

| Feature | Result | Notes |
| --- | --- | --- |
| Body text | Reliable | Words, order and content come back accurately from any PDF with a text layer. |
| Paragraph grouping | Reliable | Wrapped lines are merged back into one paragraph using per-block right margins, line pitch and indentation. |
| Bold and italic | Reliable | Read from the embedded font names, which is how the producer encoded the weight in the first place. |
| Headings | Good | Detected by relative type size and promoted to Heading 1, 2 or 3, so the Word navigation pane works. Occasionally a large emphasized line is promoted that should not be. |
| Bulleted lists | Good | Detected from the marker character, which is stripped and replaced with real Word list formatting. |
| Numbered lists | Good | Detected from patterns such as 1. and (a) and 2.1.4, and rebuilt as a real numbered list. |
| Page size | Exact | Taken from the PDF page box, or overridden to A4 or US Letter. |
| Reading order | Good on single column | Multi-column layouts are read across the page rather than down each column, because a PDF states no reading order. The multi-column note in this guide has the fix. |
| Tables | As text | Table content arrives as text. Use PDF to Excel instead, which detects columns properly and gives you a real grid. |
| Images | Not carried in text mode | Use Pages as pictures if the images matter, which keeps the page exactly as it looks. |
| Exact fonts | Not carried | The document is written with Calibri as its base font. Type size relationships are preserved, absolute typefaces are not. |
| Exact line breaks | Not carried, deliberately | The point of an editable document is that it reflows. Preserving PDF line breaks would give you a file where every line is its own paragraph. |
| Headers and footers | Included as text | They are glyphs on the page like any other, so they arrive in the flow. Delete them once rather than on every page. |
| Form fields | Not carried | Interactive form values are annotations rather than page content. |

### Multi-column documents

A PDF does not record that a page has two columns, and there is no flag anywhere in the file that says so. It records glyphs at coordinates. Your eye supplies the columns. Read a two-column academic paper strictly left to right across the full width of the page and you get the first line of the left column followed by the first line of the right one, repeated all the way down, which is interleaved nonsense. Every converter in this class has that problem, expensive commercial ones included.

Two things help. First, convert one page at a time and reassemble, which keeps the damage local. Second, and far more effective: if the document is a report you or a colleague produced, export a Word file from the original source rather than converting the printed PDF of it, because every reconstruction problem on this page disappears when the structure was never thrown away. The whole point of this tool is the case where the source is gone.

**Use it for what it is good at.** Recovering the text of a contract whose Word original was lost years ago and whose only surviving copy is the PDF somebody emailed you. Getting a supplier's terms into a document you can mark up. Pulling one section of a specification out of a 90 page manual. Those all work. Reproducing a designed brochure so that it looks identical to the original does not work, and no browser-based converter in this class manages it whatever its marketing page claims.

## The Word File You Actually Get

The output is a real .docx, not a renamed HTML file and not a rich text document with a misleading extension. It is a ZIP package containing WordprocessingML, and it opens natively in Microsoft Word, LibreOffice Writer, Google Docs, Pages and every mobile Office app.

Inside it:

- **Six styles, not ninety.** Normal, three heading levels, List Paragraph and Hyperlink, and that is the entire style sheet. A converted document arriving with ninety latent styles nobody chose is harder to work with than one carrying the six a person will actually apply, and every name used here is a name Word already recognizes, so the Styles gallery behaves normally instead of filling up with entries called Style17.
- **Real heading styles.** Not bold text pretending to be a heading. That means the navigation pane in Word populates, the automatic table of contents generator finds them, and restyling every heading in the document at once is a single click in the Styles gallery rather than 40 manual selections.
- **Real numbering definitions.** Two of them, one bulleted and one decimal, each carrying five indent levels. Lists behave as lists: press Enter at the end of one and Word supplies the next number, press Tab and it demotes to the sub-level, exactly as it would in a document you typed yourself. A converted list that is really a run of paragraphs each starting with a hyphen does none of that.
- **Correct whitespace handling.** Every text run is marked to preserve spaces. Without that, Word collapses leading and trailing spaces the moment the file opens, and words weld themselves to their neighbors across run boundaries, which is a class of corruption that is very hard to spot and very annoying to fix.
- **Clean XML.** Control characters that XML cannot legally carry, and the lone surrogate halves that text extraction sometimes produces when a font maps a glyph oddly, are stripped before the file is written. Leave even one of them in and Word refuses to open the document, reporting only that it is corrupt and naming neither the byte nor the reason.

### Pages as pictures mode

When the source is a scan, this mode renders each page at 96, 150, 200 or 300 dots per inch and places it into the document as a full-page image, with the Word page sized to the PDF page and zero margins so the image sits edge to edge. Choose 150 for something to read on screen, 200 to print, and 300 only when you genuinely need archival quality and can accept the file size, which rises roughly with the square of the resolution.

## Zero-Trust: Your PDF Never Reaches Our Server

Think about what people actually convert in this direction. A contract they need to counter-draft. An invoice with the bank details that somebody in accounts now wants retyped into a template. A tenancy agreement. A medical letter, a payslip, a settlement, a will. A tender response that has to be filed on Friday and currently exists only as a PDF. The reason somebody reaches for a PDF to Word converter is almost always that the document matters and the Word original is gone, which makes it exactly the wrong class of file to hand to a server you do not control.

The usual architecture is an upload form, a queue, a conversion process on somebody's server and a temporary download link. Every one of those documents crossed the internet and was written to a disk you do not control, retained for a period you cannot verify, in a jurisdiction you did not choose.

This converter has no upload endpoint, because there is no server-side step for one to feed. Your PDF is opened with the browser File API, parsed by JavaScript on your processor, and the Word file is assembled in memory and handed back as a Blob your own browser downloads from itself. No queue. No temporary link. The file exists on your disk and in your RAM, and nowhere else.

### Confirm it yourself

1. Open developer tools, switch to the Network panel, and clear it.
2. Convert a PDF. Watch the requests.
3. You will see the engine scripts load once and one small JSON call carrying nothing but a tool name. No request contains your document.
4. The definitive test: load this page, disconnect from the network completely, then convert. It still works, which no tool that posts your document to a server for processing could ever manage.

The PDF document properties do not travel into the Word file either. Author, producer, creation date, and any custom fields the originating system wrote, such as the case reference a legal e-filing platform stamps into every document it exports, are all left behind. The .docx carries a title, a creation timestamp and a producer string. Nothing else.

## When the Result Is Wrong, and What It Means

| Symptom | Cause | Fix |
| --- | --- | --- |
| This PDF has no text layer | It is a scan: a photograph of a page with no characters in it. | Switch to Pages as pictures, or run OCR first and convert the searchable PDF that produces. |
| Every line is its own paragraph | The document has an unusual layout, or the text was emitted line by line by an old producer. | Fix it in Word with Find and Replace on paragraph marks, or accept it and reflow the sections you need. |
| Two columns are interleaved | A PDF records no reading order, so a two-column page is read across rather than down. | Convert one page at a time to keep the damage local, or go back to the original source document if it exists. |
| Words are welded together | The producer emitted runs with no space characters and unusually tight spacing. | Find and Replace in Word usually catches the pattern. This is a property of the source file rather than the conversion. |
| Text is nonsense but looks like words | The PDF carries a bad OCR text layer from a skewed or low quality scan. | Re-run OCR at higher quality on a straightened scan, then convert. |
| Too many headings | Detection promoted emphasized lines that were not headings. | Switch Detect headings off and apply them yourself, or fix the few that are wrong in the navigation pane. |
| A table came out as loose text | Table structure is not reconstructed in this direction. | Use PDF to Excel for the table, which detects columns from glyph positions and gives you a real grid, then paste it into Word. |
| The file is enormous | Pages as pictures at 300 dpi. | Drop to 150 dpi. File size rises roughly with the square of the resolution. |

### A workflow that saves time

1. Convert with the defaults first and read the result screen: it tells you the page count, the paragraph count and how many headings were detected.
2. Open the document and check the navigation pane before reading a word. If the heading structure is right, the rest usually is.
3. Fix structure top down: headings first, then lists, then paragraphs. Never start by editing sentences, because a paragraph you have just retyped gets re-merged the moment you correct the heading above it.
4. If the structure is badly wrong, re-run once with Detect headings off and Keep a page break at each page on. A flatter document is sometimes faster to fix than a wrongly structured one.

## Frequently Asked Questions

### Is my PDF uploaded to your server?

No. The conversion runs in your browser on your own processor, and the PDF is never transmitted anywhere. Confirm it in thirty seconds: load this page, disconnect from the internet entirely, then convert anyway. It still works, because there is no server-side step for it to depend on, and no converter that uploads your file could pass that same test. This matters more here than in most directions, because the documents people convert back to Word are contracts, invoices, tenancy agreements and medical letters.

### Why is my converted Word document empty?

Because the PDF is a scan: a photograph of a page, with no characters inside it for the converter to rebuild. The conversion stops and tells you so, rather than handing you an empty document and letting you discover the problem in Word an hour later. Test any file in thirty seconds by trying to select a sentence with your mouse. If nothing highlights, it is a scan. Switch to Pages as pictures to get every page as a full-page image inside a Word document, or run optical character recognition first and then convert the searchable PDF it produces, which does give you editable text.

### Will the formatting be exactly the same as the PDF?

No. A PDF contains glyphs at coordinates with no paragraphs, no lists and no reading order, so the Word file has to be inferred from where the characters happen to sit on the page. Text content, paragraph grouping, bold and italic, headings and list structure come back reliably. Exact typefaces, exact line breaks, images in text mode and complex page design do not, and no converter in this class manages otherwise. Every case is listed in a table above.

### Is the output a real .docx file?

Yes. It is a genuine ZIP package containing WordprocessingML, with a style sheet, real heading styles and real numbering definitions inside it. Several free converters hand you a renamed HTML file or a rich text document with .docx on the end, which opens in Word and then behaves strangely the moment you touch the styles or generate a table of contents. This one does not do that. It opens natively in Microsoft Word, LibreOffice Writer, Google Docs, Pages and the mobile Office apps.

### Does it keep the headings from my PDF?

Yes, detected by relative type size. Lines set noticeably larger than the body median are promoted to Heading 1, 2 or 3 depending on the ratio, and they are written as real Word heading styles rather than as bold text. That means the navigation pane works, the automatic table of contents works, and restyling the whole document is one click. Occasionally an emphasized line is promoted that should not be. Switch Detect headings off if your document confuses it.

### What happens to tables in the PDF?

Their content arrives as text rather than as a Word table. Rebuilding a grid needs column detection, which works by reading where text sits horizontally across the page and is a completely different algorithm from paragraph detection, and it lives in the PDF to Excel tool in this suite instead. Mostly tables? Convert it there and paste the grid into Word. If your file is mostly prose with one table in it, convert here and rebuild that single table by hand.

### Can I edit the text after converting?

Yes, that is the entire point. Paragraphs are real paragraphs that reflow when you type, headings are real heading styles, and lists are real numbered and bulleted lists rather than paragraphs starting with a hyphen. Every text run is marked to preserve whitespace, which stops Word collapsing spaces on open and welding words together, a subtle corruption that is very hard to spot afterwards.

### Why do multi-column documents come out interleaved?

Because a PDF does not record that a page has columns. Your eye supplies them. Read a two-column academic paper straight across the full width of the page and you get line one of the left column followed by line one of the right column, repeated down the whole page as interleaved text, which every converter in this class produces including expensive commercial ones. Convert one page at a time to keep the damage local, or go back to the original source document if it still exists.

### What resolution should I use for Pages as pictures?

150 dots per inch for something to read on screen, 200 to print, and 300 only when you genuinely need archival quality. File size rises roughly with the square of the resolution, so a 40 page document at 300 dpi is about four times the size of the same document at 150. Most people want 150. Pages as pictures is the right mode for a scan, and for a signed contract you only need to countersign, it is often exactly enough.

### Does the Word file keep the original fonts?

Type size relationships are preserved. Absolute typefaces are not. The document is written with Calibri as its base font, and relative sizes are kept, so a heading set at twice the body size in the PDF is still twice the body size in Word. Preserving the exact typeface would mean lifting the embedded font file out of the PDF and packaging it into the Word document. That raises licensing questions about redistributing a commercial font, and it produces a file most people cannot edit comfortably anyway.

### Does the Word file keep the PDF author and metadata?

No. The author, producer, creation date and any custom fields the originating system wrote are not copied, because the Word file is assembled from the reconstructed text rather than derived from the source. The .docx carries a title, a creation timestamp and a producer string, and nothing else.

### Can I convert several PDFs at once?

Yes. Drop them all in and they are read in sequence into one Word document, in card order, which you can rearrange by dragging a card to a new position before you convert. Want them as separate documents? Run them separately. The batch limits are 20 files and 100 MB for anonymous visitors and free accounts, and 100 files and 500 MB on CartHacker Premium.

### Is there a page limit or a watermark?

No watermark, no logo, no trial banner, no attribution required, and the output is free for commercial use. No page limit either. A very long document is bounded by the memory in your own machine rather than by policy, and a 500 page file will run out of headroom on a phone long before it does on a desktop. Anonymous visitors get one operation per 12 hours, a free CartHacker account gets two, and CartHacker Premium removes the counter entirely. An operation is one conversion run, however many pages went into it.

### Does it work on a phone?

Yes. The whole engine is JavaScript and runs on any current mobile browser, which makes it a practical way to get an emailed PDF into an editable document without installing anything. Keep the batches modest, since a phone tab has far less memory headroom than a desktop one, particularly in Pages as pictures mode where each page is held as a bitmap while it is encoded.

## The rest of the PDF suite

All of these run the same way: your file is read by JavaScript on your own machine, the work happens on your processor, and the result is handed back to you as a download that never existed anywhere else.

Organize PDF

- [Merge PDF](https://carthacker.com/pdf-tools/merge-pdf/)
- [Split PDF](https://carthacker.com/pdf-tools/split-pdf/)
- [Remove Pages](https://carthacker.com/pdf-tools/remove-pages/)
- [Extract Pages](https://carthacker.com/pdf-tools/extract-pages/)
- [Organize PDF](https://carthacker.com/pdf-tools/organize-pdf/)
- [Scan to PDF](https://carthacker.com/pdf-tools/scan-to-pdf/)

Convert to PDF

- [JPG to PDF](https://carthacker.com/pdf-tools/jpg-to-pdf/)
- [PNG to PDF](https://carthacker.com/pdf-tools/png-to-pdf/)
- [WebP to PDF](https://carthacker.com/pdf-tools/webp-to-pdf/)
- [AVIF to PDF](https://carthacker.com/pdf-tools/avif-to-pdf/)
- [GIF to PDF](https://carthacker.com/pdf-tools/gif-to-pdf/)
- [BMP to PDF](https://carthacker.com/pdf-tools/bmp-to-pdf/)
- [Word to PDF](https://carthacker.com/pdf-tools/word-to-pdf/)
- [PowerPoint to PDF](https://carthacker.com/pdf-tools/powerpoint-to-pdf/)
- [Excel to PDF](https://carthacker.com/pdf-tools/excel-to-pdf/)
- [HTML to PDF](https://carthacker.com/pdf-tools/html-to-pdf/)

Convert from PDF

- [PDF to JPG](https://carthacker.com/pdf-tools/pdf-to-jpg/)
- [PDF to PNG](https://carthacker.com/pdf-tools/pdf-to-png/)
- [PDF to WebP](https://carthacker.com/pdf-tools/pdf-to-webp/)
- [PDF to AVIF](https://carthacker.com/pdf-tools/pdf-to-avif/)
- [PDF to GIF](https://carthacker.com/pdf-tools/pdf-to-gif/)
- [PDF to BMP](https://carthacker.com/pdf-tools/pdf-to-bmp/)
- PDF to Word
- [PDF to PowerPoint](https://carthacker.com/pdf-tools/pdf-to-powerpoint/)
- [PDF to Excel](https://carthacker.com/pdf-tools/pdf-to-excel/)
- [PDF to HTML](https://carthacker.com/pdf-tools/pdf-to-html/)
- [PDF to PDF/A](https://carthacker.com/pdf-tools/pdf-to-pdfa/)
- [PDF to Markdown](https://carthacker.com/pdf-tools/pdf-to-markdown/)

Edit PDF

- [Rotate PDF](https://carthacker.com/pdf-tools/rotate-pdf/)
- [Add Page Numbers](https://carthacker.com/pdf-tools/add-page-numbers/)
- [Add Watermark](https://carthacker.com/pdf-tools/add-watermark/)
- [Crop PDF](https://carthacker.com/pdf-tools/crop-pdf/)
- [Edit PDF](https://carthacker.com/pdf-tools/edit-pdf/)

PDF Security

- [Unlock PDF](https://carthacker.com/pdf-tools/unlock-pdf/)
- [Protect PDF](https://carthacker.com/pdf-tools/protect-pdf/)
- [Sign PDF](https://carthacker.com/pdf-tools/sign-pdf/)
- [Redact PDF](https://carthacker.com/pdf-tools/redact-pdf/)

Optimize PDF

- [Repair PDF](https://carthacker.com/pdf-tools/repair-pdf/)
- [OCR PDF](https://carthacker.com/pdf-tools/ocr-pdf/)

Free CartHacker tools

## Free speed test and trust badges for Shopify and WooCommerce stores

Find the apps that slow your store down, by name and in milliseconds, then answer shoppers' doubts with trust badges under Add to cart. **Both are free, with no card and no access to your store admin.**

Store Speed Test

### Which app is slowing your store down?

Paste any page and get its three Core Web Vitals, **the apps costing time, like Klaviyo or Judge.me**, and the Shopify or WooCommerce fix.

- 1 free test a day, no sign-up
- 5 a day on a free account
- Google's Lighthouse engine

Trust Seals & Badges

### Do shoppers hesitate at Add to cart?

Show the promises that settle doubts, from free shipping to a money-back guarantee, **right under the Add to cart button**. One line in your theme.

- 8 badges in 2 styles, free
- Premium: 50 badges, 30 languages
- View counts from the first shopper

[Build my trust badges](https://carthacker.com/trust-badges/#builder) Design them without signing up.

Also free

[QR Code Generator](https://carthacker.com/qr-code-generator/)

Change the link after printing and count the scans. **5 tracked codes on a free account**, static codes unlimited.

- Logo and colors
- SVG for print
- Wi-Fi and business cards

---

Source: [PDF to Word Converter - PDF to DOCX Online Free - CartHacker](https://carthacker.com/pdf-tools/pdf-to-word/), CartHacker.

## Free tools from CartHacker

- [Store Speed Test](https://carthacker.com/store-speed-test/): Check your store's Core Web Vitals for free.
- [Core Web Vitals Monitoring](https://carthacker.com/core-web-vitals-monitoring/): Monitor your store's Core Web Vitals every day, for free.
- [Trust Seals & Badges](https://carthacker.com/trust-badges/): Add trust badges under your Add to cart button.
- [QR Code Generator](https://carthacker.com/qr-code-generator/): Make a QR code you can still change after printing.
- [PDF Tools](https://carthacker.com/pdf-tools/): 39 free PDF tools that run in your browser: merge, split, convert to and from Word, Excel and JPG, sign, redact and protect. No file is ever uploaded.
- [CartHacker Premium](https://carthacker.com/premium/): one subscription, monthly or yearly, that upgrades every tool at once:
  - 50 trust badges in 30 languages, switched automatically
  - 180 days of Core Web Vitals, per page
  - All 39 PDF tools, unlimited and never uploaded
  - 200 QR codes, tracked and editable after printing
  - No ads on any guide or tool
  - Every new guide 2 weeks before the public
  - Product Feed Manager and new tools included
- Every quota and price, tool by tool: https://carthacker.com/llms.txt