How to Convert Word to JPG: Every Method Compared

A Word document is not an image, and no tool converts DOCX to JPG “directly” in any meaningful sense. A .docx file is a ZIP archive full of XML describing paragraphs, styles, and layout rules. A JPG is a flat grid of pixels. To convert Word to JPG, something has to render the document first — lay the text out on virtual pages — and then rasterize those pages into pixels.

Every method in this guide is some variation of that two-step process. Once you understand it, you can pick the route that matches your volume and quality needs instead of trusting a random converter website with your contract, resume, or client proposal.

Why Convert a Word Document to JPG at All?

The most common reasons:

The “preventing edits” case deserves a caveat: a JPG stops casual editing, but it is not protection. Anyone can run OCR on the image and recover editable text — our image to Word guide covers exactly how. If confidentiality matters, use a PDF with permissions or simply don’t send the content.

Pick Your Method First

Method 1 is the backbone of everything else — even methods 2–4 usually end with “save as PDF” as their first half. Learn it once and the rest are shortcuts.

Method 1: Export to PDF, Then Render to Image

This is the most faithful route because PDF preserves the exact page layout Word computed — fonts embedded, line breaks fixed, margins locked. Then a rasterizer turns each page into pixels at whatever resolution you choose.

Step 1: Get a PDF

Any of these produce an identical-quality PDF:

• Microsoft Word: File → Save As → PDF (or File → Export → Create PDF).
• Google Docs: File → Download → PDF Document (.pdf).
• LibreOffice Writer: File → Export As → Export as PDF.
• Windows, any app: Print → choose Microsoft Print to PDF as the printer.
• macOS, any app: Print → PDF dropdown → Save as PDF.

Prefer the app’s native “Save as PDF” over printing when available. Native export embeds fonts and keeps hyperlinks; printing re-renders through a print driver and occasionally shifts spacing.

Step 2: Render the PDF to JPG

Three free command-line tools do this well. They all need the PDF as input, which is why step 1 comes first.

pdftoppm (ships with poppler-utils, the reference renderer):

# One JPG per page, 150 DPI, named page-1.jpg, page-2.jpg, ...
pdftoppm -jpeg -r 150 document.pdf page

ImageMagick (uses Ghostscript under the hood):

magick -density 150 document.pdf -quality 90 page-%02d.jpg

Ghostscript directly:

gs -sDEVICE=jpeg -r150 -dJPEGQ=90 -o page-%03d.jpg document.pdf

All three accept -r 300 (or -density 300) for print-quality output. See the DPI section below before picking a number.

If you would rather click than type, any reputable online converter will happily take your PDF — just make sure you upload the PDF, not the DOCX. Uploading the PDF means the converter only has to rasterize; it does not have to interpret your document, which is where web converters most often mangle layouts. Our PDF to image guide compares tools and settings for that step in depth.

Method 2: Windows — Print to PDF, Then Convert

No Microsoft Word license? Windows can still produce the PDF half:

1. Open the DOCX in WordPad, LibreOffice, or Google Docs.
2. Press Ctrl+P and select Microsoft Print to PDF.
3. Save the PDF anywhere.
4. Render it with pdftoppm, or open it in the Photos app after converting.

For the image half without a terminal, Paint works for single pages: open the rendered image, resize if needed, and Save As → JPEG. Clunky but zero-install.

One Windows-specific trap: Microsoft Print to PDF does not embed all fonts by default. If your document uses a font that isn’t installed on the machine doing the conversion, Windows substitutes a fallback and the output looks different from what the author intended. This is the single most common cause of “the converted file looks wrong.”

Method 3: macOS — Preview Export

On a Mac, once you have the PDF:

1. Open the PDF in Preview.
2. File → Export.
3. Choose JPEG as the format, set the Quality slider, and save.

Preview exports one JPG per selected page, so for multi-page documents either repeat per page or use pdftoppm from Homebrew (brew install poppler) to get every page in one command. Preview’s resolution control is limited compared to -r 150/-r 300; for anything beyond a quick thumbnail, the command line gives more predictable results.

Method 4: The Google Docs Route

Upload the DOCX to Google Drive, open it with Google Docs, then File → Download → PDF, and render the PDF as above. Or skip Docs entirely: right-click the file in Drive → Download, and Drive converts some formats directly.

What to expect from the Docs route:

• Simple documents: Near-perfect. Headings, bold, lists, and standard tables survive intact.
• Complex layouts: Text boxes, SmartArt, tracked changes, custom headers/footers, and exotic fonts frequently shift or drop.
• Fonts: Docs substitutes missing fonts with its own library. If your document depends on a specific typeface, convert from the machine that has it installed.

Google Docs is the best free option when you don’t have Word — just proofread the result against the original before publishing it anywhere.

Method 5: Screenshots — When You Only Need Part of a Page

Sometimes you don’t want the whole page. You want the pricing table, or the signature block, or one chart. A screenshot is faster than any conversion pipeline:

• Windows: Win+Shift+S (Snipping Tool) captures a region straight to clipboard.
• macOS: Cmd+Shift+4 captures a selected region to a file.
• Zoom in first. Capture at 150–200% browser or app zoom so text stays crisp.

Screenshots capture exactly what’s on screen — including rendering quirks — which makes them both the quickest and least reproducible method. Fine for a one-off Slack message; wrong tool for anything you’ll repeat.

Method 6: Batch Conversion at Scale

Converting five documents by hand is fine. Converting five hundred is a scripting problem, and the standard pipeline is two commands:

# Step 1: DOCX -> PDF (all files in ./docs, output to ./pdf)
soffice --headless --convert-to pdf --outdir pdf docs/*.docx

# Step 2: PDF -> JPG at 150 DPI
pdftoppm -jpeg -r 150 pdf/*.pdf jpg/page

LibreOffice’s headless mode runs the same layout engine as the desktop app, with no window server required — it works on CI servers, Docker containers, and Raspberry Pis. Install with apt install libreoffice-writer poppler-utils on Debian/Ubuntu.

Two operational notes for production use:

• Fonts must be installed on the converting machine. In Docker, add your font files and run fc-cache -f in the image build.
• Run conversions serially or lock LibreOffice. Parallel soffice instances share a user profile and can deadlock; use -env:UserInstallation=file:///tmp/lo_$$ to give each process its own profile if you must parallelize.

A Python Wrapper

import subprocess
from pathlib import Path

def docx_to_jpg(docx_path: Path, out_dir: Path, dpi: int = 150):
    """Render every page of a DOCX as a numbered JPG."""
    out_dir.mkdir(parents=True, exist_ok=True)

    subprocess.run(
        ["soffice", "--headless", "--convert-to", "pdf",
         "--outdir", str(out_dir), str(docx_path)],
        check=True,
    )
    pdf_path = out_dir / (docx_path.stem + ".pdf")
    subprocess.run(
        ["pdftoppm", "-jpeg", "-r", str(dpi),
         str(pdf_path), str(out_dir / docx_path.stem)],
        check=True,
    )

docx_to_jpg(Path("report.docx"), Path("output"))

A Node Wrapper

import { execFile } from "node:child_process";
import { promisify } from "node:util";
import path from "node:path";

const run = promisify(execFile);

export async function docxToJpg(docxPath, outDir, dpi = 150) {
  await run("soffice", [
    "--headless", "--convert-to", "pdf",
    "--outdir", outDir, docxPath,
  ]);
  const pdfPath = path.join(
    outDir,
    path.basename(docxPath, ".docx") + ".pdf",
  );
  await run("pdftoppm", [
    "-jpeg", "-r", String(dpi), pdfPath,
    path.join(outDir, path.basename(docxPath, ".docx")),
  ]);
}

Both wrappers assume LibreOffice and poppler are on the PATH. For a hosted alternative, document-conversion APIs exist, but the self-hosted pipeline above handles thousands of documents per hour on a modest machine at zero marginal cost.

Choose the Right DPI

DPI determines pixel dimensions. A US Letter page (8.5 × 11 inches) renders as:

Rules of thumb:

• Web and social: 150 DPI is the sweet spot. Text is fully legible, files stay small, and nobody can tell the difference from 300 DPI on a screen.
• Print: 300 DPI minimum. Anything lower shows visible softness on paper.
• OCR or archival: 300 DPI, and consider PNG output instead of JPG (see below).

A4 is slightly narrower and taller than Letter (210 × 297 mm ≈ 8.27 × 11.69 in), so at 150 DPI an A4 page is about 1240 × 1754 pixels. The ratios hold regardless of page size.

Fidelity Pitfalls

These are the issues that generate most “my converted document looks broken” complaints:

Missing fonts. The converting machine must have every font the document uses, or it silently substitutes. Symptoms: different line breaks, overflowing text boxes, changed page counts. Fix: install the fonts, or convert on the machine where the document was authored.

Page breaks move. Word computes pagination from font metrics and printer settings. The same DOCX can break onto different page counts in Word vs LibreOffice vs Google Docs. If exact pagination matters, convert with the same application that produced the file.

Multi-page means multiple JPGs. JPG has no concept of pages. A ten-page document becomes page-01.jpg through page-10.jpg. If you need one file, you want PDF (or TIFF); if you need one image, pick the page you need before converting, or render only that page:

# Render only page 3
pdftoppm -jpeg -r 150 -f 3 -l 3 document.pdf page

Text boxes and shapes drift. Floating elements anchored to paragraphs can shift when a substitute engine reflows text. There is no clean fix other than converting with the original application.

Hyperlinks die. JPG carries no links. If clickable links matter, ship the PDF alongside the images.

When PNG Beats JPG for Documents

JPG compression was designed for photographs. Text is its worst-case input: high-contrast edges trigger visible ringing artifacts (“mosquito noise”) around letters, especially at quality settings below ~85.

Practical middle ground: render text-heavy pages as PNG at 150 DPI, then convert to JPG at quality 90+ only if file size demands it. You lose little sharpness and often halve the size. Switching output format is a one-flag change — pdftoppm -png instead of -jpeg.

Once your pages are images, treat them like any other image asset: compress them deliberately (our guide to converting any image to JPG covers quality settings), and if you serve document previews on a website, host them on an image CDN so they’re delivered resized and cached. For galleries of multi-page previews with deep-zoom browsing, Sirv Media Viewer handles the zoom and pan interactions out of the box.

Quick Reference

# The whole pipeline in three lines (Linux/macOS):
soffice --headless --convert-to pdf --outdir . document.docx
pdftoppm -jpeg -r 150 document.pdf page          # all pages
pdftoppm -jpeg -r 300 -f 1 -l 1 document.pdf hi  # page 1, print quality

Frequently Asked Questions

Can I convert Word to JPG without installing anything?

Yes. Open the document in Google Docs, download it as a PDF, then use any reputable online PDF-to-JPG converter. Two browser tabs, zero installs. The quality ceiling is what Google Docs can reproduce of your layout — fine for simple documents, risky for complex ones.

Why does my converted JPG look blurry?

Almost always a resolution problem. Converters that default to 72 or 96 DPI produce screen-resolution output that looks soft when zoomed or printed. Re-render at 150 DPI for web use or 300 DPI for print, and the text will sharpen up immediately.

How do I convert only the first page?

With pdftoppm, add -f 1 -l 1 to render just page one — useful for generating document thumbnails in bulk. Most graphical tools let you delete the pages you don’t want from the PDF first, or you can export a single page from Preview on macOS.

Is JPG or PDF better for sending a document?

PDF, in nearly every case. It keeps all pages in one file, preserves links and searchable text, and opens identically everywhere. Convert to JPG only when the destination genuinely requires an image — a social post, a slide deck, or a form that accepts pictures only.

Can I convert Word to JPG on my phone?

Yes. In the Word mobile app or Google Docs, share or export the document as a PDF, then use your phone’s built-in tools — iOS saves PDFs as images from the share sheet, and Android apps like Google Drive’s built-in viewer plus a screenshot handle the rest. For regular phone-based conversion, a dedicated converter app gives cleaner one-tap results.

Wrapping Up

Converting Word to JPG is always a two-step render: document → PDF → image. The PDF intermediate is not overhead — it is what locks your layout before pixels exist, and it is why the faithful routes beat “direct” converters. Match the DPI to the destination (150 for screens, 300 for print), install your fonts on whatever machine does the work, and reach for PNG when the page is mostly text.

And if the end goal is sharing rather than pixels, remember the simplest option: the PDF itself. It is smaller than ten JPGs, keeps its links, and opens everywhere.

Want your document previews served fast at any size? Create a free Sirv account and deliver them from a global image CDN.

Sources

• Ghostscript documentation
• LibreOffice documentation