html2image
A package acting as a wrapper around the headless mode of existing web browsers to generate images from URLs and from HTML+CSS strings or files.
Runssource: GitHubPythonMITcommit 81c0609f57c1
Python, MIT licensed. The project labels itself: chrome, chromium, chromium browser, css, headless browser, html, html2image and python.
html2image runs. An Argusic agent installed it in 30 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Package installed in venv, ChromiumHeadless defaults include --no-sandbox, 17 Chrome tests pass, CLI produces correct images, Edge tests gracefully skipped.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Chrome/Chromium browser found on the system15 minutes
- Chrome crashes with 'No usable sandbox' error (requires --no-sandbox)3 minutes
- Edge browser tests fail because msedge is not installed2 minutes
- pip 26.x internal error: cannot import name 'importlib' from pip._internal.metadata1 minute
- System pip blocked by PEP 668 externally-managed-environment1 minute
- Install time
- 30 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pytest tests/test_main.py -v exited 0 with 17/17 passed; hti --html-string '<h1>CLI Works</h1>' --size 400,200 produced a 400x200 PNG verified with PIL; screenshot from Html2Image constructor + screenshot(html_str=) produced valid 1920x1080 PNG
- Model tokens used
- 205,926
- Exact commit tested
- 81c0609f57c1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Fix 2**: Edge tests are conditional on browser availability; only Chrome tests run when Edge is… - **Tests**: `pytest tests/test_main.py -v` — 17/17 passed - **CLI**: `hti --html-string '<h1>CLI Works</h1>' --size 400,200 --save-as cli_test.png` — produce… tokens used 205,926 Now let me wrap up the verification. The important facts I've observed: - **Install**: `pip install -e ".[dev]"` in venv succeeded — package builds and installs - **Chrome**: Not pre-installed; installed via `playwright install chromium` → Chrome for Testing 1… - **Fix 1**: Added `--no-sandbox` to ChromiumHeadless default flags (same approach as the project's… - **Fix 2**: Edge tests are conditional on browser availability; only Chrome tests run when Edge is… - **Tests**: `pytest tests/test_main.py -v` — 17/17 passed - **CLI**: `hti --html-string '<h1>CLI Works</h1>' --size 400,200 --save-as cli_test.png` — produce…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 30 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 chrome projects Argusic has installed and timed, html2image was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
chromechromiumchromium-browsercssheadless-browserhtmlhtml2imagepythonpython3
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/html2image)Questions
- Does html2image run?
- Yes. html2image runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test html2image?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 81c0609f57c1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test html2image?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does html2image take to install?
- 30 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does html2image need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing html2image?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does html2image compare with the alternatives?
- Of the 4 chrome projects Argusic has installed and timed, html2image was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for html2image?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.