Repository navigation
Releases
v0.3.0-beta.9
Blitz-based renderer CLI, built from 35aba3e4f61a118b4717eb790d8081c18e6e3d4f.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.9_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.9
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.9_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.9_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.
v0.3.0-beta.8
Blitz-based renderer CLI, built from d24ff5c76922aba16e01e6b655865f9d9193f34d.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.8_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.8
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.8_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.8_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.
v0.3.0-beta.10
Blitz-based renderer CLI, built from 5e59bdeb10728a608acfca856610c2009c4c6907.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.10_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.10
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.10_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.10_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.
v0.3.0-beta.7
Blitz-based renderer CLI, built from aaa26bae5ce214f2216348a1f8d27a81dded211f.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.7_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.7
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.7_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.7_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.
v0.3.0-beta.6
Blitz-based renderer CLI, built from 49506d16c8648baf4333a510982e0147a82ed506.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.6_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.6
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.6_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.6_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.
v0.3.0-beta.5
Blitz-based renderer CLI, built from a50e65eaca73be3497680ba9d5ede54dc7856be9.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.5_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.5
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.5_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.5_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.
v0.3.0-beta.4-r2
Blitz-based renderer CLI, built from e730eac6fdd3a429abd3cb7841e0d5c83289e88e.
Dynamically linked, not static: the Runtime deps row below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.4-r2_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.4-r2
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.4-r2_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.4-r2_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440, in --scroll mode: 5.37 s
against headless Chromium's 13.36 s — 2.49x faster. Mode matters: the default
--clip mode on the same deck takes 5.72 s, so the headline is the fastest mode,
not the one you get without asking. The RSS figures published for that deck —
93.4 MiB against 858 MiB — are largest single process, not the process tree;
measured on a deck in the repo, Chromium's tree peaks 5.7-6.1x above its
largest process while html-render is one process, so the real memory gap is
wider than the 9.19x those two numbers give. 4.13% of pixels differ by more than
16 levels (glyph antialiasing, not layout), and ten renders of the same input are
byte-identical for documents whose resources are local or data: URIs.
Every figure is reproduced from your own deck with
python3 tools/gates.py --deck <path>; see GATES.md at this tag.
v0.3.0-beta.4-r1
Static Blitz renderer CLI, built from 30cf9e5c49c2db7ea72958d5e49a2dbd7058e451.
| Asset | blitz-render_0.3.0-beta.4-r1_linux_amd64.tar.gz |
| Binary | blitz-render (single file, no runtime deps) |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | =0.3.0-beta.4 (see Cargo.toml at this tag) |
Install:
V=v0.3.0-beta.4-r1
N=blitz-render_0.3.0-beta.4-r1_linux_amd64
BASE="https://github.com/leshchenko1979/blitz-render/releases/download/$V"
curl -fsSL -O "$BASE/$N.tar.gz"
curl -fsSL -O "$BASE/checksums.txt"
sha256sum -c checksums.txt
tar xzf "$N.tar.gz"
install -m755 blitz-render /usr/local/bin/blitz-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.56 s / 95 MiB
against headless Chromium's 13.36 s / 858 MiB. 4.13% of pixels differ
by more than 16 levels (glyph antialiasing, not layout), and ten
renders of the same input are byte-identical.
Geometry parity against Chromium is measured on every push by the
parity workflow; results are uploaded as artifacts.