Can I capture a live URL instead?

The .htm extension is the eight-dot-three sibling of .html, a holdover from Windows 3.x and early DOS web tooling that capped extensions at three characters. You still encounter .htm files in three places: legacy corporate intranets running on IIS 4 vintage installs, single-page email archives saved from Outlook 2003, and old Microsoft help documentation distributed on CD-ROMs. The content is identical to .html; only the suffix differs. Converting to HEIC produces a screenshot of the rendered page in the space-efficient HEVC-compressed format - roughly half the bytes of a JPG capture at the same quality.

heic.now renders the .htm in a headless Chromium instance at a configurable viewport (default 1280px wide), captures the full scrollable height, and encodes a HEIC that matches what a modern browser would display. Embedded resources resolve via base href or relative path; if the page depends on assets in a sibling folder, zip the whole bundle and upload that. JavaScript executes by default so dynamic content renders, though we cap script time at a few seconds to avoid runaway pages.

Common scenarios include IT auditors capturing snapshots of decommissioned intranets, archivists building large page-capture libraries where HEIC's smaller footprint compounds across thousands of captures, and writers grabbing reference shots of old documentation into Apple Photos. For litigation or portals that demand universally readable evidence, convert the capture onward with /heic-to-jpg or wrap it via /heic-to-pdf. For modern HTML5 markup, our /html-to-heic path is identical - the extension is purely cosmetic.

Reasons to convert HTM to HEIC usually come down to compatibility, file-size, or specific feature requirements. Common situations:

• An app or platform only accepts HEIC uploads.
• You need a feature unique to HEIC (e.g. transparency, vector scaling, animation, multi-page pages, etc.) that HTM doesn't provide.
• You're optimising file size — modern formats often produce smaller files than the older format you started with.
• You need a single archival format across a project so files behave consistently in the same viewer.

1. Open the HTM → HEIC tool on heic.now.
2. Drag your HTM file onto the drop zone, or click Select files. You can drop a whole folder of files at once.
3. The output is fixed to HEIC. If the format supports extra options (page size, transparency background, quality, EXIF stripping), tweak them in the right-hand panel.
4. Click Convert. The job runs on our server and finishes in a few seconds for typical photos.
5. Download the result. Files stay in storage for 24 hours and are then permanently deleted.

The entire flow is free for the first 10 jobs per day with no signup required. A free account doubles that quota; a premium plan removes the limit entirely.

• Zip the .htm with its _files folder so embedded CSS and images resolve correctly.
• Set viewport width to match the original design - 1024px for late-1990s pages, 1280px for early-2000s.
• Disable JavaScript in the source HTML if dynamic banners or popups interfere with the capture.
• For long pages, expect a tall image; consider splitting with an image editor if it exceeds 20,000px height.
• Pages with frameset markup need each frame captured separately - browsers render them as a grid.