Free URL Redirect Generator
Create a URL redirect in seconds — no signup. Enter a destination, pick the redirect type (301, 302, 303, 307 or 308), and you get a public endpoint URL. Anything that hits it — a browser, a webhook sender, a link — is instantly forwarded to your target with a real HTTP Location redirect, and every request is captured so you can see exactly what came in.
Free and instant. The redirect endpoint stays active for 48 hours of inactivity — for a permanent, authenticated redirect use a Webhook Relay account.
Need the reverse — capture and inspect incoming webhooks without redirecting? Use the free Webhook Tester (Bin). Forwarding webhooks between servers or to localhost? See webhook forwarding.
What is a URL redirect?
A URL redirect (also called URL forwarding) is an HTTP response that tells the client — usually a browser, but it can be any HTTP client — to go somewhere else. Instead of returning content, the server replies with a 3xx status code and a Location header pointing at the new address. The client then automatically requests that address. It's how http://example.com ends up at https://www.example.com, how a moved page sends visitors to its new home, and how a short or vanity link expands to its real destination.
The generator above creates a real endpoint that does exactly this. You don't need a server, DNS changes or a deploy — you get a public URL immediately, and you choose whether the redirect is temporary or permanent and whether it preserves the HTTP method and body. Because the endpoint is a Webhook Bin, it also records every request that passes through, which makes it handy for debugging clients, link tracking and migrations.
301 vs 302 vs 307 vs 308 — which redirect should I use?
The status code you pick changes how clients, browsers and search engines treat the redirect. The two things that differ are whether the move is permanent (cached, and link equity passed on) and whether the original HTTP method and body are preserved.
| Code | Name | Permanent? | Keeps method | Use it for |
|---|---|---|---|---|
301 | Moved Permanently | Yes | No (→ GET) | A page or URL has permanently moved; pass SEO ranking to the new URL. |
302 | Found | No | No (→ GET) | Temporary detour — maintenance, A/B tests, geo or device routing. |
303 | See Other | No | No (→ GET) | After a POST, send the client to a result page with a GET. |
307 | Temporary Redirect | No | Yes | Temporary move that must preserve POST/PUT method and body — APIs, webhooks. |
308 | Permanent Redirect | Yes | Yes | Permanent move that must preserve the method and body — API/webhook endpoints. |
Rule of thumb: use 301 when a page has permanently moved and you want search engines to pass ranking to the new URL; use 302 for a temporary detour (maintenance, A/B tests, geo-routing). If the original request was a POST, PUT or DELETE and you need the method and body to survive the redirect — as you do when forwarding a webhook — choose 307 (temporary) or 308 (permanent). A classic 301/302 will turn the follow-up request into a GET and drop the body, which silently breaks API and webhook traffic.
What you can do with it
- Forward a deprecated webhook URL to its replacement with a 307/308 so the method and JSON body are preserved.
- Point an old or vanity link at its new destination without standing up a server or touching DNS.
- Test how a client follows redirects — does your HTTP library follow 307? Does it re-POST? Watch the captured request to find out.
- Migrate an endpoint gradually: send traffic to the new host while the captured log shows you exactly who's still calling the old one.
- Share a single stable link in a doc, email or QR code and change where it points later by editing the bin.
How it works
When you create a redirect, we provision a Webhook Bin and configure its response to redirect. Each incoming request is logged and then answered with your chosen status and a Location header:
$ curl -i https://bin.webhookrelay.com/v1/webhooks/<id>
HTTP/1.1 302 Found
Location: https://example.com/destination
Content-Length: 0 A browser follows that header automatically and lands on the destination; curl -L or any HTTP client that follows redirects does the same. Meanwhile the request is captured in the bin, so you can inspect the method, headers, query string, body and client IP of everything that hit the link.
URL redirect vs URL shortener
A URL shortener is one specific use of redirects: it maps a short, branded slug to a long destination, usually with click analytics. This generator is lower-level and more flexible — you control the exact status code (301/302/303/307/308), it preserves the request method and body when you need it to (so it works for API and webhook traffic, not just links), and it captures the full request for inspection. If all you want is a tidy short link, a shortener is simpler; if you're debugging clients, forwarding webhooks or testing redirect behaviour, this gives you the control and visibility a shortener won't.
Frequently asked questions
How do I create a URL redirect?
Enter the destination URL above, choose a redirect type (302 temporary by default, or 301 permanent), and click Create redirect URL. You get a public endpoint immediately — every request to it is forwarded to your destination with an HTTP Location redirect. No signup, server or DNS change required.
What is the difference between a 301 and a 302 redirect?
A 301 is permanent: clients and search engines cache it and pass link equity to the new URL. A 302 is temporary: clients keep using the original URL and ranking is not transferred. Use 301 for permanent moves and 302 for temporary detours.
Which redirect keeps the POST method and body?
Use 307 (temporary) or 308 (permanent). Unlike 301/302 — which most clients turn into a GET and strip the body — 307 and 308 make the client repeat the original method and body, so they are correct for redirecting API calls or forwarding webhooks.
Is the URL redirect generator free?
Yes, completely free and no signup. The endpoint is a Webhook Bin that stays active for 48 hours of inactivity. For a permanent, authenticated redirect with custom domains, create a Webhook Relay account.
Can I see who hits the redirect link?
Yes. Because the endpoint is a Webhook Bin, every request is captured before the redirect is returned. Open Inspect captured requests to see the method, headers, query string, body and client IP of everything that follows the link.
Does the redirect work for webhooks and API calls, not just browsers?
Yes. Any HTTP client that follows redirects will be forwarded. For POST/PUT/DELETE traffic such as webhooks, choose 307 or 308 so the method and request body are preserved across the redirect.