Shlink Web Client
Shlink Web Client is the official web interface for Shlink, a self-hosted URL shortener.
Platform availability
Available on 2 of 9 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
75/100 Good
- Maintained
- 100last commit 11 days ago
- Popular
- 52401 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 100128 MB minimum RAM, runs on ARM
Availability: platform listings confirmed today, links checked 42 days ago
- GitHub stars
- 401
- Open issues
- 3
- Last commit
- 2026-10-31
- Latest release
- v4.9.0
- License
- MIT
- Activity
- steady
Checked 8 days ago - source: GitHub (shlinkio/shlink-web-client)
Resources & Compatibility
Minimum requirements: 128 MB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 43 days ago - source: Docker Hub image tags and published docs
First-install notes
- Check the health endpoint after starting After the app starts, request the /rest/health endpoint (you can type it into a browser or use a terminal tool like curl). This quick check tells you whether the Shlink service is answering; if it fails, your short links and web interface will not work yet. source
- Test that short links redirect Once a short link exists, open it in a browser to confirm it jumps to the intended long URL. This tests the public redirect path that visitors use, so if it does not redirect correctly, people clicking your links will see errors. source
- Shlink server setup Run a Shlink server first, then generate an API key with the CLI command shlink api-key:generate and add that key to the client's servers.json file. source
Fetched 26 days ago - each note links to its source
Variants
Alternatives (8)
- Beacons - Create a free, beautiful, and highly customizable link in bio website with Beacons.
- Dub.co - Open-source link management with analytics, free QR code generation, custom domains, advanced audience targeting, team collaboration, and S…
- Fli.so - Fli.so is a lightning-fast URL shortener built with SvelteKit and PocketBase.
- Polr - Like everything else here, Polr is an open source and self-hostable web application.
- Shlink - A self-hosted URL shortener application that lets you create and manage shortened links under your own domain, with both command-line and R…
- TinyURL - Converts long URLs into short, secure links, supports branded domains, bulk shortening via API, link analytics, QR code generation, and das…
- YOURLS - YOURLS is a free, open-source self-hosted URL shortener that lets you create shortened links on your own server, with analytics, plugins, a…
- bit.ly - Shortens URLs, generates customizable QR codes, tracks clicks, offers branded domains, bulk management, analytics, browser extension, and A…
Checked 30 days ago - source: AlternativeTo
Common questions
How do I serve the self-hosted web client without dynamic routes returning 404?
Configure the web server to fall back to index.html when the requested file does not exist because the app uses a client-side router. Apache is covered by the included .htaccess, and nginx can use the same approach as the Docker config.
What port should I expose for the Docker image?
The Docker image serves the static app on port 8080.
Can I preconfigure Shlink servers and API keys before first use?
You can place a servers.json file in the project root with the server name, URL, and API key starting with version 2.1.0. Otherwise, the first browser configuration is stored in local storage and can be exported or imported.
How can I add authentication when reverse-proxying the web client?
One reverse-proxy setup adds an Authelia redirect in the web client's advanced configuration for authentication.
What should I try first if the self-hosted client cannot see the Shlink server?
Test the same Shlink server using the hosted web client first to isolate the problem from your self-hosted client.
Answers sourced from github.com, www.reddit.com, www.reddit.com
Community
- SH-Link Web Client cannot see SH-Link server : r/selfhosted - Reddit (reddit)
- Shlink/Shlink Web App Reverse Proxy : r/selfhosted - Reddit (reddit)
- Shlink - Apps (forum)
- Shlink.io Great Docker to short urls - SynoForum.com (forum)
Collected 43 days ago - public community threads