How it works
From long URL to filed link
No setup, no browser extension, no learning curve. Here's the whole workflow, start to finish.
The workflow
Paste the destination
Any URL — a landing page, a form, a listing, a document. If you forget the https://, we add it.
Name the slug
Pick something readable like /spring-launch, or leave it blank for an auto-generated slug. If a slug is taken, we'll say so — we never silently reassign.
Label and note it
Optional, but this is what keeps a library from becoming a junk drawer. A label groups it; a note explains it.
Share it — and re-route it whenever
Copy the short link anywhere. When the destination needs to change, edit it from your dashboard. The link itself never changes.
Anatomy
What's in a short link
Under the hood
What happens on a click
A visitor hits your short link, our server looks up the current route, and forwards them with an HTTP 302 redirect. We use 302 (temporary) rather than 301 (permanent) deliberately — it tells browsers not to cache the hop, so when you re-route a link, everyone goes to the new destination right away.
What visitors see
The forward is immediate — no interstitial page, no countdown, no ads between the click and the destination. Your link behaves like a direct link that happens to be shorter.
Slug rules
Lowercase letters, numbers, and dashes. No slurs, no impersonating system paths like /login or /admin. First come, first served; deleted slugs are retired, not resold.
Abuse handling
Links routing to malware, phishing, or scams get disabled when found or reported. That protection is what keeps the domain trusted — which keeps your links deliverable. Report a link.
See it from the inside
The dashboard preview is open — no account needed to look around.