Skip to main content
When your app is ready, you have two options for what to do with it: download it as a file you keep and host yourself, or publish it directly to a public URL. Both options produce something you can share with anyone — the difference is in how much control you want over where it lives.

​
Export to HTML

Click the Export button in the toolbar to download your app as a single, self-contained HTML file. The file works in any modern browser, can be hosted anywhere that serves static files, and requires no build step or server to run. Open the downloaded file directly in a browser, drag it onto a hosting service, or drop it into any static file host — it’s ready to go immediately.
For a free and instant way to share your exported app, try Netlify Drop: drag your HTML file onto the page and Netlify gives it a public URL in seconds. GitHub Pages and Cloudflare Pages are also free options if you want the file in a repository.

​
Deploy to a Public URL

Deploying to a public URL is available on appblips.com only. This feature is not available in self-hosted installations.
On the hosted version of AppBlips, you can publish any app directly to its own public URL. Click Deploy and AppBlips assigns the app a dedicated link you can share with anyone. Deployed apps are installable as Progressive Web Apps (PWAs), so visitors on mobile can add them to their home screen and use them like a native app. When deploying, you can optionally add password protection to restrict access to the published URL. Only people who know the password will be able to open the app — useful for tools you want to share with a specific group without making them fully public.

​
The Exported File

The downloaded HTML file is fully self-contained: all styles, logic, and structure are bundled into a single document with no external dependencies on AppBlips. Once you have the file, it works on its own — open it, host it, or email it, and it runs the same way every time. If your app uses the AI features (the blip.ai API), the AI connectivity configuration — whether that’s a BYOK prompt or a relay endpoint — is embedded in the exported file. The app carries everything it needs to prompt users for their AI credentials or connect to a relay, with no extra setup required. In the default BYOK (bring your own key) setup, the exported file never contains an API key. Instead, the first time someone uses an AI feature in the exported app, a small Connect your AI provider dialog appears. The user enters their own API endpoint, model name, and key. Their key is stored only in that browser — in session storage by default, or local storage if they choose Remember on this device.
AppBlips never bakes an API key into exported HTML. Anyone who opens an exported app with AI features will be asked to supply their own key when they first use an AI-powered feature. This is by design — make sure anyone you share the file with understands they’ll need their own OpenAI-compatible API key to use those features.