font-render-client
Command-line client of the Font Render Service: send fonts (TTF, OTF, WOFF, WOFF2) to a Windows server that renders them with DirectWrite in headless Chromium, get PNG waterfalls back.
uv tool install font-render-client # or: pipx install font-render-client
font-render login http://studio-pc:41800 # asks for your token (from the server's admin)
font-render MyFont.ttf # waterfall 9-24 ppem -> ./renders/
font-render A.ttf B.ttf --ppem 9-40 # compare fonts
font-render MyFont.ttf --plain --zoom 4 # text only, 4x nearest-neighbour
font-render --info # server and which client you are
Fonts are sent to the server and kept in its memory only; the server never writes them to disk.
| Command | |
|---|---|
font-render login [SERVER] [--token T] [--admin-token T] [--dev-token T] |
Check the token against the server and save it (~/.config/font-render/config.toml, %APPDATA%\font-render\config.toml on Windows) |
font-render login --show / font-render logout |
Show (tokens masked) / delete the saved settings |
font-render FONT... [--ppem 9-24] [--text ...] [--scale 1.5] [--plain] [--zoom N] [--invert] [-o DIR] |
Render (PNG into ./renders/ or DIR) |
font-render-batch DIR_A DIR_B |
Render font pairs across browsers |
font-render-clients list|add|rotate|disable|enable|remove|settings |
Manage client tokens and access settings (admin token) |
font-render --update / --rollback |
Update the server to the newest release / go back (admin token) |
font-render --install-browser chromium|firefox|webkit |
Install a browser engine on the server (admin token) |
font-render --deploy [REF] / --deploy --local / --release |
Developer mode only (dev token) |
Every command takes --server URL (-s) to talk to another server than the saved one.
The server address is the server computer's name or IP — the install summary on the server
lists them (http://STUDIO-PC:41800, http://studio-pc.local:41800, http://192.168.1.23:41800).
Settings can also come from the environment or a .env file in the current directory:
FONT_RENDER_SERVER, FONT_RENDER_CLIENT_TOKEN, FONT_RENDER_ADMIN_TOKEN,
FONT_RENDER_DEV_TOKEN; they take precedence over the saved settings.
1 maintainer
Metadata
1 maintainer
Release files for font-render-client 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| font_render_client-1.1.0.tar.gz | 14.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| font_render_client-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.7 kB
Release files / font_render_client-1.1.0.tar.gz
| Download URL | font_render_client-1.1.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
809dd0769bf4887c23f4dcfb94269e7b209ce1485c9f33c530384cdab2fee47b
|
|
BLAKE2b-256 checksum How to use checksums |
6f5101eb9de2283e5d16fdccd75a372cca21b2b5031f8470cec8955078760d92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logRelease files / font_render_client-1.1.0-py3-none-any.whl
| Download URL | font_render_client-1.1.0-py3-none-any.whl |
|---|---|
| Size | 18.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b54d73e76d56ed135714d39c5847465db0413cc2f1238996cc859afb548e2477
|
|
BLAKE2b-256 checksum How to use checksums |
ebd5d01a3bb002267d5ba85ef4b2f7f123827d7cee8953c71d63d39c08e27b04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logSecurity for font-render-client 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for font_render_client-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
