Images to Word — Several per Page, in a Grid

Q: Can I put multiple images into one Word document?

Yes, and in a grid rather than one per page. Pick 1–4 columns and how many rows per page; the images fill the grid in order and a new page starts when it is full. Two columns by three rows gives six per page, which is the usual contact-sheet shape. The grid is a real Word table, so you can still edit, move or delete any cell afterwards.

Q: Why is my Word file so much smaller than the images I added?

Because Downscale to printed size is on. A 12-megapixel phone photo printed 60 mm wide only needs about 700 pixels across at 300 dpi — the other eleven and a half million pixels make the document enormous and change nothing you can see. Turn it off if you want the full-resolution originals embedded, and expect a file tens of times larger.

Why this is harder than it looks

Dragging twenty photos into Word one at a time and nudging each to the same size is an afternoon's work, and the moment you change the margins it all moves. The reliable way to line pictures up in a Word document is to put them in a table and hide the borders — that is exactly what this tool builds, so the result behaves properly when you edit it afterwards.

Because it is a real table and real inline images, nothing is flattened. Open the .docx and you can drag a picture bigger, retype a caption, add a row, or switch the borders back on to see the grid.

What the other tools do instead

Search "image to Word" and almost everything you find is an OCR tool: it reads the text out of your picture and throws the picture away. That is a genuinely useful thing — we have PNG to Word and Image to Text for it — but it is not what you want when the images are the content. Of the tools that do place the picture, most take one image and fit it to the page width, with nothing to adjust.

Feature	Typical OCR tools	Single-image placers	This tool
Keeps the picture	No — text only	Yes	Yes
Many images, one document	One at a time	One at a time	Yes
Grid — columns × rows	No	No	Up to 4 across
Exact printed width	No	Page width only	mm, inches or px
Page size, orientation, margins	No	Fixed	Yes
Caption under each image	No	No	Editable
Keeps the file small	n/a	Embeds full resolution	Downscales to printed size
iPhone HEIC photos	Usually rejected	Usually rejected	Decoded in-browser
Images leave your device	Uploaded	Usually uploaded	Never

Capabilities at a glance

What this tool does and does not do, stated plainly. The “No” rows are the point, not an omission.

Capability	Supported	Detail
Input
PNG, JPG, GIF, BMP	Yes	Embedded directly — .docx declares a type for each.
WebP and AVIF	Yes	Re-encoded first: .docx has no type for either.
iPhone HEIC	Yes	Decoded in the browser; the decoder loads only when you add one.
SVG and JFIF	No	Deliberately not offered — the document would refuse the file.
Several images at once	Yes	That is the whole tool — drop as many as you like.
Reordering	Yes	Drag a card, or use the arrows beside it.
Layout
Several images per page	Yes	1–4 columns × rows per page, in a real Word table.
Exact printed width	Yes	In millimetres, inches or pixels — what it measures on paper.
Page size and orientation	Yes	A4, Letter, Legal or A3, portrait or landscape.
Margins	Yes	Narrow, normal or wide.
Gap between images	Yes	In millimetres.
Captions under each image	Yes	Filename, full filename, Figure N, or none.
Mixed layouts in one document	No	One grid applies throughout.
Cropping or rotating	No	Use our crop and rotate tools first.
Output
A real .docx, editable in Word	Yes	Built with the docx library — not a renamed .zip or an .html.
Opens in Google Docs, LibreOffice, Pages	Yes	It is standard Office Open XML.
Transparency survives	Yes	A transparent PNG stays transparent — unlike the PDF route, where a page has no alpha.
Downscale to printed size	Yes	Optional, and it is where nearly all the file size goes.
Searchable text	No	A photo of text stays a picture — run OCR if you need the words.
Password protection	No	Word can add one after the fact; this tool does not.
How it runs
Nothing is uploaded	Yes	The document is built on your device and never sent anywhere.
Signup, watermark or daily limit	No	None of the three.
Offline use	No	The page and its Word library load from the network first.

The file-size trap

This is the part that catches people out. A picture placed 60 mm wide in a Word document prints at roughly 450 pixels across. If you embed a 4000-pixel phone photo at that size, Word stores all 4000 pixels and displays 450 of them — so twenty holiday photos become a 90 MB document that will not go through email.

With Downscale to printed size on, each image is re-encoded at twice its printed width before it goes in. Twice, not exactly, because a good printer resolves around 300 DPI and screen sizing assumes 96 — the doubling covers printing and any later resizing without keeping pixels nobody will ever see. Transparent images stay PNG; opaque ones become JPEG, since a photograph re-encoded as PNG is routinely ten times larger.

Making a contact sheet

Set columns to 3 and rows per page to 4 for twelve frames a page, captions to File name so every frame is labelled, and orientation to landscape with narrow margins if you want them bigger. Photographers use this for client proofs; site engineers use it for dated survey photos; teachers use it for worksheets. It is the same grid either way.

iPhone photos and AVIF

A photo straight off an iPhone is usually HEIC, and no browser will decode one to a canvas — Safari can display it, but the pixels cannot be read back. So HEIC is handled by a real decoder that loads the first time you add one and never otherwise; the file is turned into a JPEG on your device before it goes into the document. Nothing is uploaded, and the original filename is still what the caption uses.

AVIF is the opposite problem: current browsers decode it natively, but the .docx format has no AVIF type at all, so it is re-encoded on the way in exactly like WebP. On a browser too old for AVIF you get a message saying so rather than a silent failure.

A note on units

Word measures embedded images in pixels at 96 DPI, not in points, which is why "60 mm" here means 60 mm on paper and not 60 mm of something else. When you type a width in millimetres or inches it is converted through 96, so what you measure with a ruler on the printed page is what you asked for.

Frequently Asked Questions

Yes, and in a grid rather than one per page. Pick 1–4 columns and how many rows per page; the images fill the grid in order and a new page starts when it is full. Two columns by three rows gives six per page, which is the usual contact-sheet shape. The grid is a real Word table, so you can still edit, move or delete any cell afterwards.

No — this is the opposite. It keeps the pictures and arranges them; OCR tools throw the picture away and give you the words. That confusion is why "image to Word" searches land on two completely different kinds of tool. If you want editable text out of a screenshot or a scan, use PNG to Word, which rebuilds headings, paragraphs and lists as real Word content.

Switch the size mode to an exact width and type a number in millimetres, inches or pixels. Every image is then placed at that measured width on the page, with its height following the aspect ratio and capped by the max-height field. It is a real printed measurement: 60 mm comes out of the printer at 60 mm. Leave it on the fitting mode instead and each image expands to fill its column, which is what you want for a contact sheet.

Because Downscale to printed size is on. A 12-megapixel phone photo printed 60 mm wide only needs about 700 pixels across at 300 dpi — the other eleven and a half million pixels make the document enormous and change nothing you can see. Turn it off if you want the full-resolution originals embedded, and expect a file tens of times larger.

Usually because the images are PNGs of photographs. PNG is lossless, so a photograph stored as PNG can be ten times the size of the same picture as a JPEG, and the document inherits that. Converting the photos to JPG first is the fix — our image compressor does it in a batch. The other cause is simply setting a very large printed width, where the pixels genuinely are needed.

No. The document is assembled in your browser by a JavaScript library, so the images never leave your device. There is no upload wait, no size cap imposed by a server, and nothing of yours sitting somewhere afterwards. That matters here because the things people put in a grid document are ID photos, evidence, inspection reports and product shots.

Yes. The grid is a real Word table and the captions are real paragraphs, so you can retype a caption, drag an image bigger, delete a row or add text around it. That is the whole reason to choose .docx over PDF here — a PDF looks identical everywhere but nobody can write in it.

PNG, JPG, GIF and BMP go in directly, because .docx declares a content type for each. WebP and AVIF are accepted and re-encoded first, since the format has no type for either — a file whose bytes disagree with its declared type is what makes Word refuse a document. iPhone HEIC works too: no browser can decode HEIC natively, so a decoder is fetched, but only when you actually add one. SVG and JFIF are not offered, because the document would refuse them.

Yes, which is the one real advantage over the PDF route. A .docx can hold a PNG with an alpha channel and Word renders it, so a logo or a cut-out keeps its transparency against whatever is behind it. A PDF page has no alpha at all, so the same image is flattened onto white there. If your images have transparency to keep, this is the format to use.

Yes, four ways: the filename without its extension, the full filename, an automatic Figure 1, Figure 2… sequence, or no captions at all. They print beneath the picture in the grid cell as ordinary Word paragraphs, so you can retype any of them afterwards.

Drop the photos in, set columns to 3 or 4, rows per page to match, leave the size mode on fitting so each photo fills its cell, and set captions to the filename. That is a contact sheet: a page of thumbnails with names under them, which is what photographers, estate agents and anyone cataloguing stock actually want — and what a one-image-per-page converter cannot produce.

It is one of the most common uses, and the reason captions matter. Photograph the defects, drop them in, use two columns so the report stays readable, and set captions to the filename if you have named the photos by location. Because the output is a real Word document you can then type findings around the pictures, which a PDF would not let you do.

Yes — they are placed in the order the cards appear, left to right and then down, so the grid reads like a page of text. Drag a card to move it, or use the arrows. Dropping files from a folder usually gives you the operating system’s order, which is not always the numeric one you expect once filenames run past nine.

A4, US Letter, Legal and A3, portrait or landscape, with narrow, normal or wide margins and a gap between images you set in millimetres. The grid is computed inside the margins, so changing the page size or margin re-flows the layout rather than cropping it.

No limit we impose — there is no server to protect. The practical limit is your device’s memory, since every image is decoded before it is placed. Hundreds of full-resolution photos on a phone is where it will struggle; leaving the downscale option on is what keeps that manageable, because the large originals are never carried into the document.

Only the captions. The images stay images, so text inside a photo or a scan is not searchable — that needs OCR. If you want the words out, run the pictures through image to text, or use PNG to Word to get an editable document instead.

Image to DOCX