Publishing with Pubby takes about 3 seconds. Here's what happens during those 3 seconds, explained simply for beginners, and in technical detail for those who want to know exactly what's happening under the hood.
Think of publishing a web page like sending a letter, but instead of one person receiving it, the whole world can read it instantly.
You visit pubby.au. You either paste your HTML code into the editor, drag a folder of files onto the page, or call the API from code. That's your input.
Behind the scenes, Pubby takes your files and stores them in a way that makes them fast to load from anywhere in the world.
Within about 3 seconds, Pubby gives you a URL like pubby.au/your-page. Anyone with that link can open your page immediately in any browser.
Your page is served over HTTPS, the secure, encrypted connection that shows the padlock icon in browsers. You don't set this up. It happens automatically.
That's it. No servers to configure, no account approvals, no waiting for DNS to propagate.
The most straightforward path. Visit pubby.au, paste HTML into the editor or drag-and-drop files, hit publish. A URL appears. Copy it, share it, done.
Best for: One-off pages, non-developers, quick previews, first-time users testing the product.
Drop an entire project folder, HTML, CSS, JavaScript, images, onto the Pubby upload zone. Pubby detects the entry point (typically index.html), stores all assets, and serves them together. No zip required, no configuration.
Best for: Multi-file projects, design exports (Figma HTML exports, Webflow downloads), static site generator output.
A single POST request to the Pubby API returns a live URL. You send your HTML as a string or as a file. You get a URL back. The entire interaction is 1 request.
POST https://api.pubby.au/publish
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"html": "<html>...</html>",
"slug": "my-page-name"
}Best for: Developers, automated pipelines, AI agents, any system generating HTML programmatically.
AI agents that produce HTML output can use the API to publish their output as a final step. No human involvement needed. The agent generates, the agent publishes, the agent returns a URL.
Best for: Automated pipelines where an AI generates content and users need a live link immediately.
When you hit publish, here's what happens inside Pubby's infrastructure in that 3-second window:
Your HTML and any associated assets (CSS, JS, images) are received, validated, and stored. Pubby checks the structure, identifies the entry point, and maps asset references (so your CSS and images load correctly relative to the HTML).
If you specified a slug (a URL name like my-page), Pubby checks it for availability and reserves it. If you didn't specify one, Pubby generates a unique one. The slug becomes the last part of your URL: pubby.au/slug.
Your files are pushed to Pubby's CDN (content delivery network), a globally distributed network of servers. When someone in Tokyo opens your page, they get it from a server near Tokyo. When someone in London opens it, they get it from a server near London. Load times stay fast regardless of where your visitors are.
Every Pubby URL is served over HTTPS automatically. For pages on pubby.au subpaths, this is instant, Pubby's wildcard certificate covers all published pages. For custom domains, Pubby provisions a Let's Encrypt certificate for your domain, which takes under 60 seconds after DNS propagation.
Once the CDN has your files, the URL becomes live. Pubby returns the URL to you. The whole process takes 2-4 seconds for typical page sizes.
On Pro, Teams, or Business plans, you can point your own domain to a Pubby page.
DNS propagation typically takes between 5 minutes and 48 hours. This is outside Pubby's control; it depends on your DNS provider and TTL settings. Once propagated, your custom domain resolves to your Pubby page with full HTTPS.
Published pages are public by default. Anyone with the URL can view the page. API keys are hashed, not stored in plain text. All stored files are encrypted at rest.
| Plan | Publishes / hour | Concurrent requests | Max file size |
|---|---|---|---|
| Free | 60 | 5 | 10MB bundle |
| Pro | 600 | 20 | 50MB bundle |
| Teams | 1,500 | 50 | 100MB bundle |
| Business | 3,000+ | 100+ | 200MB bundle |
Pages have no traffic limits. If your page gets 100,000 hits in an hour, the CDN handles it. Individual file limit: 50MB. Total page bundle: 200MB.
See the documentation for API reference, rate limit specifics, and detailed guides on each publishing path.