File Hosting & Sharing

Public URL

Definition

A public URL is a web address whose content is returned to every request that reaches it. There is no account check and no signature in the query string, so the address works the same in an email, a browser bookmark, a slide deck or someone else's page. On a host like 99helpers a file gets one the moment it is published, typically in the form your-name.99helpers.site, and it stays stable while the file is replaced underneath it. A public URL is not automatically a direct link: some hosts give you a viewer page that wraps the file in their own interface, and only the direct address returns the raw bytes. Public also does not mean listed — nothing has to appear in a search engine for the address to work.

Why It Matters

Public is the setting that makes a thing usable. An image cannot appear in an email template, a PDF cannot be opened from a QR code, and a font cannot load into a site unless the address answers without a login. The same property is what people misjudge: an unguessable address is not a permission system, and a URL leaks the moment it is pasted into a chat tool, a support ticket or a browser that syncs history. Treat anything with a public URL as readable by strangers, and put a password or an expiry in front of the handful of files where that is not acceptable.

How It Works

Opening a public address is the ordinary web path with nothing extra bolted on. DNS resolves the host name to an edge address, TLS negotiates the connection, and the server matches the path — the URL slug plus any file name — to a stored object. It answers 200 with the bytes and a Content-Type header, having checked no identity at any point. Whether search engines index the address is decided separately, by robots.txt and by whether anything anywhere links to it; blocking crawlers hides the page from results but leaves it perfectly reachable to anyone with the string. Caching headers then let edge nodes hold a copy, which is why a public file usually gets faster after the first request in a region.

Real-World Example

A charity publishes its annual report at harbourside-annual.99helpers.site and prints the address on the back of a leaflet. No reader needs an account, and the address survives the site being rebuilt because it points at the published file rather than at a folder on somebody's laptop. When next year's report is ready the charity uploads it to the same address, and the leaflets already printed keep working.

Common Mistakes

  • Relying on a long random address as security — a public URL is one paste away from being seen, and hosting logs, referrer headers and chat previews all copy it around
  • Confusing a viewer page with the file itself, then embedding the wrapper address in an img tag and wondering why nothing renders
  • Blocking crawlers and calling the file private — robots.txt only asks well-behaved indexers to look away
  • Changing the address to tidy up naming, which silently breaks every printed leaflet, email and bookmark already in circulation

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →