Merge Images, CSV, and Markdown Into One PDF (2026)

TL;DR

You can drop a mix of images, a CSV spreadsheet export, and a Markdown note into one drag-and-drop area and get a single PDF — files placed in the exact order you list them, each rendered the way it should be. The Convert: Anything to PDF extension does this entirely inside your Chromium browser (Chrome, Edge, Brave, Arc, Opera, Vivaldi). There's no merge limit beyond your device's memory, no watermark, and — the part paid "merge PDF" tools can't match — nothing uploads. Your files never touch a server.

Here's the concrete scenario this post is built around: a real-estate agent has 3 property photos (JPG), a pricing sheet (CSV), and a Markdown cover note, and needs one polished PDF to send a client. By the end you'll know exactly how to build that, and why doing it locally beats sending confidential pricing to Smallpdf or iLovePDF.

The problem with "attach the files"

The lazy version of this task is emailing five separate attachments and hoping the client opens them in the right order. It looks unprofessional, it's easy to lose a file, and a wide CSV opened in a spreadsheet app on the client's phone is a pinch-and-zoom nightmare.

The other common version is stitching everything together in Word or Google Docs — paste the photos, screenshot the spreadsheet, retype the cover note. That's twenty minutes of fiddling, and the "screenshot of a table" always comes out blurry.

Merging into one PDF fixes both. One file, in order, rendered cleanly. The only question is how you merge — and that's where the local-vs-upload distinction matters.

The scenario: a listing packet in one PDF

Say you're the agent. Your five source files:

1. cover-note.md — a short Markdown note: greeting, the pitch, next steps.
2. photo-front.jpg, photo-kitchen.jpg, photo-yard.jpg — three phone photos.
3. pricing.csv — the pricing breakdown exported from your CRM or a spreadsheet.

You want the client to open one PDF that reads: cover note first, then the three photos in walkthrough order, then the pricing table on its own page. Here's the full flow.

Step by step: the drag-drop merge

1. Open the extension and choose Upload Files

The extension has two paths — This Page (captures the tab you're viewing) and Upload Files (converts files from disk). Merging is an Upload Files job. Click it.

2. Drag all five files in at once

Select the Markdown note, the three JPGs, and the CSV, and drag them into the drop area together. You don't have to add them one at a time, and you're not restricted to a single file type — mixed formats in one merge is the whole point.

3. Order them the way the client should read them

Arrange the list so the merge happens in the exact order you want the pages:

1. cover-note.md
2. photo-front.jpg
3. photo-kitchen.jpg
4. photo-yard.jpg
5. pricing.csv

The output PDF follows this order top to bottom. Get the sequence right here and the document reads like a deliberate document, not a pile of attachments.

4. Pick paper size and orientation

Choose a base paper size — A4, US Letter, US Legal, or Tabloid. For a US client, Letter is the safe default. Orientation is set per conversion, and there's a smart exception coming up for the CSV.

5. Convert

One click. The extension builds a single PDF locally using jsPDF, and the finished file is ready in seconds. No upload, no queue, no download-from-server round trip.

What happens to each file type inside the merge

The reason this beats a generic "combine PDF" tool is that each file is rendered appropriately for its type — you're not pre-converting everything to PDF yourself first.

That CSV behavior is the quiet hero. A pricing sheet with, say, unit, sq ft, list price, price/sq ft, HOA, and taxes is 6 columns — and it automatically lands in landscape so nothing gets squeezed off the page. You don't configure it; wide tables just breathe.

Images keep their quality — there's no re-compression that turns your listing photos muddy. And the Markdown cover note comes out as typeset text you (and the client) can select and copy, not a picture of text.

No merge limit — really

There's no cap on how many files you combine. The only ceiling is your device's memory, so a packet with 3 photos is trivial, and a 60-page inspection bundle with dozens of scans works the same way. No "upgrade to merge more than X files" wall — a very common friction point on freemium tools.

Bigger scenario: A consultant assembling a project close-out — a Markdown executive summary, 20 site photos, a CSV of line-item costs, and a JSON export of the ticket log. Same flow, one PDF, in order. The full 14-format guide covers every input type you can throw into a merge.

Why local matters more than usual here

Merging is exactly the situation where uploading is worst, because the files you merge into a client deliverable are almost always sensitive: pricing, personal photos of a property, cost breakdowns, internal notes.

With the paid "merge PDF" tools — Smallpdf, iLovePDF, and the like — your files travel to their servers to be combined, then come back. That's a copy of your confidential pricing and property photos sitting on third-party infrastructure, however briefly.

Here, zero network requests fire during conversion. The merge runs on your machine. Concretely, that means:

• Confidential by construction. The pricing sheet and photos never leave your laptop. Nothing to trust, nothing to log. This is the core argument in why a PDF converter should not upload your files.
• Faster. No upload of 20 high-res photos, no server queue, no download. It's as fast as your machine.
• Works offline. Building a packet from a coffee shop with flaky wifi, or on a plane? It doesn't need the internet, because it never uses it.

If privacy is a firm requirement across your workflow, the privacy-first file conversion guide lays out what to look for.

Compared to paid merge tools

The paid tools shine when your inputs are already PDFs and you just need them stapled together at scale with server-side muscle. But when your inputs are raw — loose photos, a CSV export, a Markdown note — this extension merges them into one PDF without a pre-conversion chore and without shipping your files off-device.

For the broader editing-suite comparison, see Smallpdf vs iLovePDF vs Convert: Anything to PDF.

A few things to know before you merge

Keeping you out of surprises:

• Excel .xlsx isn't read directly. Export the pricing sheet to CSV first (Excel: File → Save As → CSV; Google Sheets: File → Download → CSV), then include the CSV in the merge. Details in the CSV to PDF walkthrough.
• GIFs use the first frame. If you're merging in a GIF, only its first frame lands in the PDF.
• No OCR. A scanned image of text merges as an image — the text won't be selectable. Text you want selectable should come from Markdown, TXT, or a text HTML file.
• HTML must be a local file for the Upload Files path. For a live web page, use This Page instead.
• Chromium only — Chrome, Edge, Brave, Arc, Opera, Vivaldi. Not Firefox or Safari.
• Output isn't password-protected. If the merged packet needs encryption, add that in a separate step.

Frequently asked questions

Can I really merge images, a CSV, and Markdown in one go?

Yes. Drag all of them into the Upload Files area at once, arrange them in the order you want the pages, and convert. The output is a single PDF where images render as images, the CSV becomes a formatted table, and the Markdown is typeset as real text.

Is there a limit on how many files I can merge?

No fixed limit. The only ceiling is your device's memory, so a 5-file listing packet and a 60-file project bundle both work the same way — no "upgrade to merge more" wall.

Do my merged files get uploaded to a server?

No. The merge runs 100% locally using jsPDF, and zero network requests fire during conversion. Your files — including confidential pricing and photos — never leave your device, and merging works offline.

How do I control the page order?

The output PDF follows the order you list the files in before converting. Arrange them top-to-bottom in the sequence you want the reader to see, then convert.

What happens to a wide spreadsheet in the merge?

A CSV is auto-formatted into a table, and if it has 6 or more columns, that section automatically switches to landscape so the table isn't squeezed. You don't have to configure anything.

Can I merge a live web page with local files?

The web-page capture (This Page) and file uploads are separate entry points. To include a web page's content in a merged PDF, save it as a local HTML file first, or capture it to PDF and handle the combine step accordingly. Local files of every supported type merge together in one pass.

Which browsers support this?

Any Chromium browser — Chrome, Edge, Brave, Arc, Opera, and Vivaldi. Firefox and Safari are not supported.

Bottom line

A client-ready deliverable is often a mix — a note, some photos, a table — and the right move is one clean PDF in a deliberate order, not five attachments. Convert: Anything to PDF merges images, CSV, Markdown, and more into a single PDF with no limit, no watermark, and no uploads — your pricing and photos stay on your machine.

Install it, build your next packet in one pass, and skip the server round trip. And when the packet's sent and it's finally quiet, CineMan AI is a free companion extension that overlays IMDb and Rotten Tomatoes ratings plus an AI Taste Match right on Netflix, Prime, and Disney+.