pickfit

BrowseDeveloper CLIs

Labelize

Parses ZPL/EPL/TSPL/CPCL/DPL labels and renders them to PNG or PDF offline.

Tested on Linux and Windows

Use it

Linux x86_64

  1. Download linux binary tarball and install to ~/.local/bin

    curl -fsSL -o /tmp/labelize-clean.tar.gz https://github.com/GOODBOY008/labelize/releases/download/v1.10.0/labelize-x86_64-unknown-linux-gnu.tar.gz && mkdir -p /tmp/lzclean && tar -xzf /tmp/labelize-clean.tar.gz -C /tmp/lzclean && mkdir -p ~/.local/bin && rm -f ~/.local/bin/labelize && cp /tmp/lzclean/labelize ~/.local/bin/labelize && chmod +x ~/.local/bin/labelize

Check that it works

labelize --help

The output should contain “Convert a ZPL/EPL/TSPL/CPCL/DPL file to PNG or PDF”.

First thing to try

cat > label.zpl <<'EOF'
^XA^FO50,50^A0N,40,40^FDHello World^FS^XZ
EOF
cat label.zpl
labelize convert label.zpl && ls -l label.png && file label.png

Run labelize convert <file> on a label file to render it to an image.

Windows x86_64

  1. download Windows binary zip from Releases

    curl.exe -sL -o labelize.zip https://github.com/GOODBOY008/labelize/releases/download/v1.10.0/labelize-x86_64-pc-windows-msvc.zip && dir labelize.zip && tar.exe -tf labelize.zip
  2. extract labelize.exe from zip

    tar.exe -xf labelize.zip && dir labelize.exe && .\labelize.exe --version
Where the README and reality differ
  • README: npm install @goodboy008/labelize-wasm provides the labelize CLI
    What worked: Used README's Windows path (download labelize-x86_64-pc-windows-msvc.zip from GitHub Releases v1.10.0 and extract labelize.exe) because the ranked npm package installs only a WebAssembly library with no labelize binary on PATH

Check that it works

tar.exe -xf labelize.zip && dir labelize.exe && .\labelize.exe --version

The output should contain “labelize 1.10.0”.

First thing to try

[System.IO.File]::WriteAllText('label.zpl', '^XA^FO50,50^A0N,40,40^FDHello World^FS^XZ') && .\labelize.exe convert label.zpl && Write-Output CONVERT_OK

Run labelize convert <file> on a label file to render it to an image.

What it does

  • Render labels to PNG and PDF
    How to use it
    1. Save your label code in a file such as <file>.zpl.
    2. Run labelize convert <file>.zpl to create <file>.png in the same folder.
    Tested
  • Turn images into ZPL or TSPL code
    Not shown working
  • Preview labels in a web playground
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 3 features work
  4. Works offline

Windows x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • preview shipping label before printing
  • batch-convert label templates to PDF for archival
  • generate label PNGs on the fly from a microservice
  • validate label content in CI with golden-file tests
  • add real-time label preview to design tools

An alternative to Labelary and Zebra Printer.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 1.10.0

Differences the test machine hit

  • README: npm install @goodboy008/labelize-wasm
    In the test: Downloaded prebuilt linux tarball labelize-x86_64-unknown-linux-gnu.tar.gz v1.10.0 from GitHub releases and copied labelize to ~/.local/bin
  • README: cargo install labelize --features cli / cargo add labelize
    In the test: Skipped; box has no Rust toolchain and installing one is forbidden, so cargo candidates cannot work here

Windows x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 1.10.0

Differences the test machine hit

  • README: cargo install labelize --features cli / cargo add labelize
    In the test: Skipped both cargo candidates: box has no Rust toolchain and installing one is forbidden, so cargo install/add cannot work here
  • README: (Windows steps)
    In the test: pickfit ran these steps in PowerShell 7 (pwsh 7.6.9) as a standard user; the built-in Windows PowerShell 5.1 is not verified and does not run `&&`.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.