Batch HTML to PDF Converter Batch HTML to PDF Converter
4.5 · 1144 votes

Download Batch HTML to PDF Converter Software and Merge Pages into One PDF

Batch HTML to PDF Converter takes a directory of saved .HTML, .HTM and .XHTML pages and writes PDFs on your Windows PC. It picks up the resources folder sitting next to each page, so the pictures land in the PDF too.

   
 Download for Free
Windows 11 / 10Free trial, no sign-up
Batch HTML to PDF Converter Screenshot.
Save a web page in any browser and you get two things on disk rather than one. There is the .HTML file, and next to it a folder named after the page, where the images and the style sheets live. Move the file on its own and the page opens blank. That split is why converting saved pages by hand goes wrong so quietly - the file looks fine and the PDF comes out with holes in it. SoftOrbits Batch HTML to PDF Converter reads the whole list at once and carries each page together with its folder. Output is PDF or plain TXT.

How to download and use the Batch HTML to PDF Converter Software

Queue the whole directory.
1

Queue the whole directory

Download the Batch HTML to PDF Converter tool and drag in every saved page you want converted. Leave the resources folders where they are. The program finds each folder by the name and keeps it with its page.

Tick Combine all pages into one PDF.
2

Tick Combine all pages into one PDF

The checkbox sits in the Output box, with Combined file name under it. Type a name there and the whole queue lands under it as one document. Order follows the list on screen, top to bottom, and the program sorts nothing by itself, so add the pages in the order you want them.

Set the format and the output folder.
3

Set the format and the output folder

Output Format offers two entries, PDF and TXT. Merging belongs to PDF. Leave the merge box ticked and switch to TXT, and the run ignores it, with a line on screen saying why. Then point the output folder wherever you want the results.

Press Start and read the summary.
4

Press Start and read the summary

Rows take a status as the queue moves down the list. A page that refuses to render is marked and skipped instead of taking the rest of the batch with it, and the count of what was skipped waits for you at the end.

Where a desktop converter earns its place

One press of Start for a directory of exports.

One press of Start for a directory of exports

Applications that produce HTML produce a lot of it. A reporting tool leaves one file per period, invoices come out of accounting packages one per customer, and a chat client writes a thread per conversation. One person on a support forum had 50-plus .HTM files and was opening each one by hand. The question was whether a macro could speed it up. Browsers never grew a mode for doing this in bulk. Drop the directory in and walk away.

   
 Download for Free

Keeping an internal report on the machine it already lives on

An upload is fine for a page you saved off a public site. It is a different decision for a payroll export, a discovery set or a dump of the internal wiki. And there is a practical catch that comes before the privacy one. A web form takes a file, while your saved page is a file plus a folder, so you end up zipping the two together by hand for every page in the pile. Without that folder the reader loses most of what the page looked like. Free web tiers then cap you at 20 pages per document, or three jobs an hour. Batch HTML to PDF Converter works on your own PC, and a sniffer over a finished run did not catch a single outgoing request.

   
 Download for Free

Keeping an internal report on the machine it already lives on.
Images that arrive with the text.

Images that arrive with the text

The complaint repeats on support forums in almost the same wording. Converted the page, got a blue question mark where the photo used to be. Sometimes the cause is a background reached through a relative path like ../images/header.jpg that the converter never resolved. More often the folder simply did not travel with the file. Nobody warns you at the time. You find out when you open the PDF, and by then the originals may already be gone.

   
 Download for Free

Forty pages in, one document out

With Combine all pages into one PDF ticked, each page renders on its own first, then the parts are stitched in the order shown on screen. A page that fails drops out of the merge. The rest still make the document.

The folder next to the page goes too

A page stored this way keeps its pictures and style sheets in a folder next to it. The name varies by browser and by language - page_files, page.files, page-files, _fichiers, _dateien. The program matches the shape of the name, not a fixed list of suffixes, so it finds those too, and the whole tree travels with the page. It skips junction points inside, which stops a link from pulling half of your drive into the job. The same page came out at 77,415 bytes over two sheets with its folder next to it, and 64,042 bytes over one without.

Deep paths still render

Pages end up far down a tree - a project folder, a date, a slug taken from the original URL. Past about 260 characters the renderer hands back a blank sheet. HTML to PDF Converter Software watches for 200 characters and stages the document into a short temporary folder first, under the plain name page.html, with its resources copied next to it. The PDF is normal, and you never see the staging folder.

XHTML from Word and CMS output

Word saves as .XHTML, and so do several content systems when you pull an article out from them. The renderer treats that markup as ordinary HTML, and the staging step hands the copy a .html name so no later step argues about the extension. .HTML, .HTM and .XHTML share one queue and one set of settings.

Plain text when the layout is in the way

Output Format has a second entry: TXT. It strips the page furniture and keeps the text. That is what you want when the thing coming next is a grep across three years of exported tickets rather than a document somebody sits down and reads. The merge switch has no say here. TXT comes out one file per page.

ultra-hd-4k

A renderer still getting updates

A lot of batch HTML tooling still runs on wkhtmltopdf, a project archived on January 2, 2023, whose last build stopped getting security patches and still carries CVE-2022-35583, an SSRF rated 9.8. This one renders through WebView2 instead, the Chromium runtime Windows 11 ships with and Windows 10 picks up through Microsoft Update. It boots once for the whole batch, about 1.9 seconds, then spends roughly a second on each document. A page that hangs gets 120 seconds of its own before the program gives up on it and moves on.

Batch HTML to PDF Converter
Batch HTML to PDF ConverterDownload the Batch HTML to PDF Converter Software, add the pages you saved, then tick Combine all pages into one PDF.
 Download

Who needs Batch HTML to PDF Converter Tool

Finance and back-office teams

Statements, invoices and period reports leave accounting packages as HTML far more often than anyone plans for. The file room wants one PDF a month, not 90 loose pages with 90 folders beside them.

Web and documentation teams

A static docs build is a directory of HTML with assets hanging off each file. So is a set of page proofs for a client. Zip that up for a reviewer and the first thing you write in the mail is which file to open. A PDF saves you that mail.

Analysts working from saved sources

Research done in a browser leaves dozens of saved pages on a drive, each with its own folder. That drive gets reimaged sooner or later. A dated PDF in the case folder outlives it, and it is still citable two years on.

Batch HTML to PDF Converter
Batch HTML to PDF Converter
Price
from $ 29.99
Version
3.8
File Size
18.5 Mb
Last updated on
23/08/26
System Requirements
  • Windows 11/10/8.1/8/7 (32/64 bit)
  • Intel i3, AMD Ryzen 5 or above
  • 4 GB of RAM or above
  • NVIDIA® GeForce® series 8 and 8M, Intel® HD Graphics 2000, Quadro FX 4800, Quadro FX 5600, AMD Radeon™ R600, Mobility Radeon™ HD 4330, Mobility FirePro™ series, Radeon™ R5 M230 or higher graphics card with up-to-date drivers
  • 1280 × 768 screen resolution, 32-bit color
  • 1 GB of free hard disk space or above

Frequently Asked Questions

Short answer: put them all in one list and press Start once. Long answer: nothing interrupts the run. The program never stops to ask about a file or to confirm the next page. Drag in the pages. Choose PDF in the Output Format box, point the output somewhere, press Start. Demo mode allows three pages a day, which covers a trial run on your own pages.

Yes. The Combine all pages into one PDF checkbox does exactly that, and the file it writes takes whatever name you give it. The list keeps the order you built it in, and the pages end up that way in the document, so drop them in the order you want them read. Merging applies to PDF output only. In TXT you always get one text file per page.

No, it converts HTML to PDF offline. The renderer starts with its networking shut down, so name lookups fail and there is nothing for the page to reach. That matters more for HTML than you would think. A saved page often still points at a style sheet or a font on somebody's CDN, and those references stay unresolved. What gets printed is what is on your disk. A page saved as Webpage, Complete, with its folder, converts whole; a bare .HTML file that leaned on remote assets converts as bare markup.

Images and CSS come through when they sit in the folder next to the page. Relative references such as ./page_files resolve the same way they did in the browser, and CSS backgrounds come with them. That part is where printing straight from a browser fails, because the Background graphics box in the print dialog is off by default and nothing reminds you. The program switches off JavaScript on purpose: you are printing somebody else's page, not running it. A page whose content appears only after a script has run will come out as the markup underneath.

No. PDF is an open format, and any renderer able to print a page can write one. A general PDF suite handles a single HTML file well enough. Ninety of them is a different job. You need every page kept with its resources folder, and a directory that runs through unattended.

Four things decide it. Each page has to stay with its resources folder. The tool has to merge a whole run into one document, and it has to do the job without sending anything off your machine. The fourth one people find out about later: what happens when a file in the middle fails. Here it gets marked in the window and the queue keeps going.

The queue itself has no file-count limit. Demo mode caps the day, not the batch. Three pages a day, with no watermark and no cap on how many pages sit inside a document. The counter resets at midnight. In merged mode the check happens before the run starts, so the program trims a list longer than what is left of the day's allowance to that number rather than failing halfway. Staging handles very long paths, and the program drops a single document that hangs for 120 seconds so the rest can finish.

Rate Batch HTML to PDF Converter

  • Windows 7
  • Windows 8
  • Windows 10
  • Windows 11
Author: SoftOrbits (English)
4.5
Avg. rating: 4.5 from 1144 votes
Good
 Download for Free

Risk-free download

progressive-webapps/apis/offline-first Created with Sketch.
100% offline
Your files never leave your PC
Safe & secure download
Directly from the official website
No sign-up required
No account or email to get started
Trusted since 2006
Desktop software for Windows