Repository navigation
[Project Showcase] labelle-web - A Web UI for Labelle #139
Description
Hey Labelle community 👋
First off, thanks for the hard work on labelle! It’s been working great for me.
I wanted to share a project I built on top of it called labelle-web.
I was originally planning to get rid of my old Dymo and buy a modern, WiFi-enabled label maker. However, I really didn't like the current products on the market (proprietary apps, cloud requirements, etc.). Finding labelle allowed me to reuse my trusty old hardware and make it "smart" myself!
What is it?
It is a lightweight web wrapper for Labelle that allows you to print labels directly from a browser. I built it specifically for "headless" setups (like a Raspberry Pi) so I could print labels from my phone or laptop without needing to SSH in or run CLI commands.
Repository: https://github.com/szrudi/labelle-web
Key Features:
- Web Interface: Clean, mobile-friendly UI to type text or upload images.
- Headless Friendly: Perfect for running as a service on a Raspberry Pi/Server.
- Powered by Labelle: It uses
labelleunder the hood to handle the actual communication with the Dymo printer.
I thought this might be useful for others looking for a way to share their label printer on the local network. Feel free to check it out or link to it if you think it fits!
Thanks again!
Activity
szrudi commentedon May 17, 2026
Update: where labelle-web is now, and an open question 👋
A few months in and I wanted to drop an update on this thread plus raise something I've been thinking about more seriously.
Since the showcase (Feb), labelle-web has grown into:
{{variable}}placeholders, SSE progress streaming, cancel mid-run, optional cut marks between labelsuhubctl(with power state persisted across container restarts), runtime version display, PWA installThe open question:
I've since seen #16 and #45 where you have discussed an eventual official "labelle-web" frontend (cc @maresb, @tomek-szczesny, @tomers, and @cr3ation since that thread referenced your project). I named my project before that discussion was on my radar (apologies for the accidental name collision).
I've been sketching some directions for a v2 - mobile-first polish first, with a more speculative template-first thesis as a possible second step - and posted it as an open brainstorm in PR #30. The direction is genuinely open; the template-first idea especially is something I'd like outside input on before committing.
Rather than continuing in isolation, I wanted to put it openly: would the maintainers be interested in talking about whether this project could be a candidate for adoption as the official labelle-web, or at least sharing thoughts on the v2 direction while it's still malleable? I'd genuinely value the input either way, and I'm equally happy to stay independent if that's the better fit.
Thanks for considering 🙏
maresb commentedon May 22, 2026
Hi @szrudi, thanks so much for creating labelle-web! For a very long time I've been wanting to create exactly this. I've been quite overwhelmed with other stuff, so it's only just now that I managed to take a look at your work. Many apologies for the delay!
I'd like to invite you and your repo to the labelle-org to make things official. I really appreciate your energy and motivation on this, and I regret that I can't match it in the moment, so I think it's best to give you free reign, because I think you're doing a spectacular job!
szrudi commentedon May 22, 2026
Hi @maresb — really appreciate the invite. No apologies needed; you've put years into labelle and it shows.
My plan for the transfer:
szrudi/labelle-web→labelle-org/labelle-web. The name matches what's been discussed in earlier issues and reflects what the repo actually is, so I'd like to keep it as-is.ghcr.io/szrudi/labelle-webwill carry a "we've moved" banner in the UI footer, so anyone on:latestfinds the new home from their browser. After transfer, releases publish toghcr.io/labelle-org/labelle-web.@tomers tagging you since you raised the "labelle needs a web frontend" thread back in #45; figured you might want to weigh in.
This is a hobby project for me too, capacity comes and goes, but I'll be here and contribute when I can. Happy to loop anyone in on direction whenever it suits.
chore(footer): add labelle-org migration banner
chore(transfer): point repo references to labelle-org/labelle-web
chore(footer): add labelle-org migration banner
chore(transfer): point repo references to labelle-org/labelle-web
chore(transfer): point repo references to labelle-org/labelle-web