Skip to main content
Here are quick answers to the most common questions about AppBlips — what it can build, how the AI works, and more.
AppBlips generates single-file HTML apps and multi-page websites. That covers a wide range of practical and creative projects: interactive tools, mini-games, dashboards, habit trackers, forms, quizzes, calculators, data visualizers, portfolio sites, and more.AppBlips is not designed for native mobile apps or full-stack web applications with complex backends. Apps it produces are fully self-contained HTML files that run entirely in the browser, and multi-page websites export as self-contained static ZIP archives.
No. AppBlips is built for anyone who can describe what they want in plain English. You do not need to know HTML, JavaScript, or React to get useful results. If you do code, you can read, export, and change everything AppBlips generates.That said, if you have some coding knowledge, more precise prompts — ones that name specific behaviors, edge cases, or UI patterns — tend to produce better first drafts and reduce the number of follow-up tweaks you need to make.
AppBlips is open source under the MIT License. You can use, modify, and redistribute it, including commercially, as long as you keep the copyright and license notice. The license text is the authoritative version.
You can use your own Anthropic, OpenAI, Gemini, DeepSeek, or OpenRouter API key, or a local model through LM Studio or Ollama. Open Settings → API, choose your provider and model, and enter its key if required. See Set up your AI provider.
In the desktop app, your API key is encrypted with your system keychain and stays on your computer. It is used only by the app’s background process when it calls your AI provider. In the browser version (run from source or Docker), AppBlips’ own server on your computer saves it in a file only you can read, never in your browser. In every version, it is never embedded in generated app code and never included in any exported HTML file.
AppBlips has no account and no cloud of its own. It connects to:
  • Your AI provider (the one in Settings → API): your prompts, your project’s code and any images you attach are sent there to build your app. LM Studio and Ollama run on your own computer.
  • GitHub: to check for new versions, when the app starts and every hour while it’s open. The desktop app also downloads updates from there. Turn this off in Settings → Workspace → Check for updates. The Microsoft Store version gets updates from the Store instead (it still checks GitHub so it can tell you a new version is out).
  • Google Fonts: for the fonts AppBlips itself uses.
  • Hugging Face: only when you build AppBlips from source or with Docker, to download the voice-input speech model once. The desktop app already includes it.
  • Web3Forms: if you turn on the Web3Forms connector in Settings → Connectors, the websites and apps you build send their form entries there, whenever someone submits a form, including in the preview. AppBlips itself only contacts it when you send a request with Request a connector or submit a project to the Showcase, and only sends what you typed in that form.
  • Umami: only if you turn on the Umami connector in Settings → Connectors. AppBlips itself never contacts it. The pages you build load its tracking script, including in the preview, but visits from the preview aren’t counted. Once your pages are online, they report each visit to your Umami dashboard.
  • Plausible: only if you turn on the Plausible connector in Settings → Connectors. AppBlips itself never contacts it. The pages you build load its tracking script, including in the preview, but visits from the preview aren’t counted. Once your pages are online, they report each visit to your Plausible dashboard.
  • tawk.to: only if you turn on the tawk.to connector in Settings → Connectors. AppBlips itself never contacts it. The websites and apps you build load its chat bubble, including in the preview, and send it the messages visitors type.
  • Square: only if you turn on the Square connector in Settings → Connectors. AppBlips itself never contacts it. The buy and pay buttons in the websites and apps you build open your Square checkout when someone clicks them, including in the preview.
  • Pollinations: only if you turn on the Pollinations connector in Settings → Connectors. AppBlips contacts it to sign you in (sending AppBlips’ public app key), to show the Pollen your sign-in has left, to make the images you ask for (sending each image’s description with your sign-in), to check a site key you paste, and to download your images when you publish or export. The websites and apps you build contact it when they show those images and when visitors use AI features or connect their Pollinations account (sending AppBlips’ public app key), including in the preview. See Pollinations.
  • Pixabay: only if you turn on the Pixabay connector in Settings → Connectors. AppBlips contacts it when you save your key (to check it), when you search (sending your search words and your key) and when you add photos (downloading them into your project). Search thumbnails load straight from Pixabay. The pages you build don’t contact Pixabay: the photos are part of your project. See Pixabay.
  • Tavily: only if you turn on the Tavily connector in Settings → Connectors. AppBlips contacts it when you save your key (to check it) and when the AI searches the web while building (sending the AI’s search words and your key, never your project’s code). The pages you build don’t contact Tavily. See Tavily.
  • SEO: no service, unless you say yes to a site scan. If you type your website address into the SEO questions, AppBlips asks first. If you agree, it visits that one page from your computer, once, and keeps only its title, description and headings. Your answers (and anything the scan read) are saved with the project on your computer and are sent only to your AI provider, as part of a build request, after you save or change them.
  • Surge: only when you use Publish to the web. AppBlips sends Surge your email and password when you sign in, and your project’s pages and images when you click Publish. See Publish to the web.
  • Code libraries (CDNs): the apps you build, and imported sites, load libraries such as React, Tailwind CSS or game engines from public sites like esm.sh, jsDelivr and cdn.tailwindcss.com. Exported apps load them from there too.
Each of these services can see your IP address when AppBlips connects. AppBlips sends no analytics or tracking.Voice input connects to nothing: the speech model runs on your computer, and your recording never leaves it.
Yes. With the Anthropic provider, AppBlips turns on prompt caching automatically. You don’t need to change any settings.A build or review takes several steps, and each step sends the AI’s instructions and the conversation so far again. Anthropic stores those repeated parts for a few minutes. When the next step reuses them, it bills them at a small fraction of the normal input price. Storing them costs a little more than normal the first time, so caching pays off from the second step on.Single quick replies, such as the short message after a build, aren’t cached, because nothing in them is sent again.You can see it working in the [anthropic] log lines in the terminal, if you run AppBlips from source, Docker or npm run desktop. See Find the error details. Other providers handle caching their own way, and AppBlips doesn’t change it.
AppBlips doesn’t show a count in the chat. Your AI provider’s usage or billing page shows what you were charged. See How much did that use?.
AppBlips no longer sells AI Credits. To build, use your own API key from an AI provider, or LM Studio or Ollama on your computer: open Settings → API, choose a provider, paste your key, pick a model and click Save. See Set up your AI provider.Questions about a plan you bought earlier? Email support@appblips.com.
This can happen with an older copy of AppBlips installed from GitHub; that installer wasn’t code-signed, so Windows could warn you or, with Smart App Control, block it. Install AppBlips from the Microsoft Store instead: it’s the only way to install on Windows now, it’s signed by Microsoft, and it updates itself. See Windows installer is blocked for details.
There is no macOS installer yet. You can run AppBlips from source with Node.js and use it in your browser, or run it with Docker.
They’re the same app. The desktop app saves your projects as folders on your computer, keeps your key in the system keychain and updates itself. The browser version (from source or Docker) saves projects in your browser and your key on your computer, and you update it yourself. Use Settings → Data → Export and Import… to move projects between them.
Yes. Use the Export option to download your app as a single self-contained HTML file, or your website as a .zip archive of pages. Apps from the App studio can also download as a React project you can keep building with npm. The exported files work in any modern web browser with no server or build step. They load styling and some libraries (such as Tailwind CSS, the Phaser game engine or a website’s carousel and animation add-ons) from public CDNs, so they need an internet connection.
Click Previous version (the left arrow in the preview toolbar), or press Ctrl+Z (⌘Z on Mac), to step back one change at a time. You can also open the history drawer from the header to see every version of your app and jump directly to any earlier state.
There is no limit imposed by AppBlips. You are only constrained by your AI provider’s rate limits and your own usage budget.