Skip to main content
The Settings modal — accessible from the header — gives you control over how AppBlips looks and behaves. It is organized into tabs: Appearance, Workspace, AI, Connectors, Tools, Data, About, and Danger Zone. Every setting is saved on your device and persists across sessions automatically.

Appearance

These settings control the visual presentation of the AppBlips interface.

Theme

Light | Dark | System
default:"Dark"
Sets the color scheme for the AppBlips interface. Light keeps the interface in a light palette at all times. Dark keeps it dark at all times. System follows your operating system’s current color scheme preference and switches automatically when your OS switches.

Build pane font

Small | Default | Large | XL
default:"Small"
Controls the text size throughout the entire build pane, including starter ideas, the conversation history, and the prompt input field. Increase this if you prefer larger text while writing or reviewing prompts.

Build pane position

Left | Right
default:"Left"
Determines which side of the workspace the build pane appears on. This setting applies on wider screens where both the build pane and the preview panel are displayed side by side.

Workspace

These settings control how the preview and build experience behaves during and after generation.

Code view

toggle
default:"On"
When enabled, a Code tab appears in the preview toolbar. Select it to inspect the raw HTML of your generated app at any time, or click Edit to change it yourself (see Edit the code yourself). Turn it off if you’d rather keep the interface focused on the live preview. Imported sites always show a Files tab instead, whatever this is set to.

Auto Follow Code

toggle
default:"On"
When enabled, the Code tab automatically scrolls to keep the most recently written line visible as AppBlips streams in the generated code. Disable this if you want to scroll back and read earlier sections while generation is still in progress.

Code autocomplete

toggle
default:"On"
When enabled, editing code in the Code tab (after clicking Edit) shows a short list of suggested words as you type. Use the up and down arrow keys to pick one, then press Enter or Tab to insert it, or keep typing to ignore the list. Escape closes it. Suggestions come from words already in your code plus common keywords, HTML tags and CSS properties. They are worked out on your computer: nothing is sent to the AI and no tokens are used. Turn it off if you’d rather type without a list popping up.

Live code preview

toggle
default:"On"
When enabled, the preview pane shows a live peek at the code being written while your app is generating. Disable this if you prefer a clean preview that only updates once the full app is ready.

Skip splash screen

toggle
default:"Off"
When enabled, AppBlips never plays the intro animation and takes you straight to the workspace. This setting takes effect on the next page load — the current session is not affected.With it off, the intro plays every time AppBlips opens or the page reloads. Click Skip in the bottom-right corner, or press Esc, to skip it.

Check for updates

toggle
default:"On"
AppBlips checks GitHub for new versions when it starts and tells you when one is out. The desktop app checks again every hour while it’s open. The desktop app on Windows and as an AppImage also downloads the update in the background and offers to restart. If you run AppBlips from source or Docker, it links to how to update. GitHub sees your IP address when AppBlips checks. The Microsoft Store version is updated by the Store, so its notice links to the Store page instead. The setting also shows which version you’re on, and a change takes effect the next time you open AppBlips.Click Check now to check straight away, even with the switch off. The answer appears under the setting: you’re up to date, a new version is available (with a link), or, where the desktop app updates itself, the update is downloading or ready with Restart to update.

Replay onboarding

Desktop app only. Click Replay to see the setup screens again: your name, chat avatar and projects folder, then the AI setup. Your current AI setup is kept unless you save a new one, and you can leave without changing anything.

AI

The provider that builds your apps comes first, then settings that influence how the AI model reasons and communicates before and during generation.

Your own provider

Choose the AI provider that builds your apps: Anthropic (the default), OpenAI, Gemini, DeepSeek, LM Studio, Ollama, or OpenRouter. Your provider is used for building, editing, reviews, and Ask mode. With Anthropic, AppBlips turns on prompt caching automatically, so the repeated parts of a build cost less. See the FAQ for how it works.
string
Your key from Anthropic, OpenAI, Google AI Studio, DeepSeek, or OpenRouter. Local servers only need a key if you turned on authentication.
string
Only for LM Studio and Ollama. The address of your local server, ending in /v1. Leave it empty to use the usual address.
select
Select a model from your provider’s live model list. Enter your API key first for cloud providers; local providers load models from your running server. Click Refresh models to reload the list, or type an exact model ID if the list can’t load. For OpenAI, use a model that supports tool calling through Chat Completions. For local servers, load a model that supports tool calling. On OpenRouter, uncensored models (such as Venice’s) aren’t listed and can’t be used.
Click Test connection to check the settings, then Save. Clear removes the saved provider and key after you confirm. If you leave the tab with unsaved changes, AppBlips asks whether to save or discard them.
In the desktop app, your key is encrypted with your system keychain and only the app’s background process uses it. In the browser version (from source or Docker), AppBlips’ own server saves it on your computer, never in your browser. It is never stored in your projects. See Set up your AI provider and Security.

Output tokens

A token is a small piece of text, roughly three-quarters of a word. These limits cap how long one AI reply can be.
number
default:"64,000"
The longest reply allowed when building, editing, reviewing or fixing code. Leave it empty to use the default of 64,000, which is enough for a large app (LM Studio and Ollama use their own default instead). Reasoning (thinking) also counts against this limit. If your provider doesn’t accept the number, AppBlips retries with the largest value the provider allows.
number
default:"Provider default"
The longest reply allowed in Ask mode. Leave it empty to let your AI provider decide.
Changes save as you type. Click Use default (or Use provider default) to clear a value.

Reasoning

Reasoning applies whenever the AI writes code: building a new app, editing one, and fixing errors.
Off | Minimal | Low | Medium | High | Extra high | Max
default:"Low"
How long the AI thinks before it writes code, for new apps and for changes. Lower levels are faster and cheaper; higher levels think harder for complex apps but take longer and use more tokens.Only the levels your provider and model support are shown, so the choices change when you pick a different model in Settings → AI. The model’s own default is marked. If you switch to a model that doesn’t have the level you picked, AppBlips uses the closest one it does have, and goes back to your choice when you switch back.
Chat-only replies (clarifying questions and Ask-mode answers) always run with reasoning off, so they stay quick.

Clarifying questions

toggle
default:"Off"
When enabled, AppBlips may ask you a clarifying question before generating — for example, to confirm the intended behavior of an ambiguous feature. This helps the AI understand your intent and can reduce back-and-forth editing, but adds a step before the first build begins.

Code Review (beta)

toggle
default:"Off"
Code Review is a beta feature, so it is off by default. When enabled, AppBlips asks after every build or edit whether anything looks wrong on screen. Choose Looks wrong and the AI tests the project in the built-in browser, reads the code, and writes a report; it takes a screenshot only when it finds a problem a picture would help confirm or show you, and adds it to the report as evidence. Choose Looks fine and it tests the project and reads the code the same way, but never takes screenshots. It doesn’t change anything itself. If the report lists problems, AppBlips asks whether to fix them. Choose Fix problems and a new chat starts with the report as its task, and the AI fixes them as a normal edit, or choose Not now to leave things as they are. Choose Looks fine but doesn’t work when the screen is right but something you tried misbehaves, and the AI focuses on clicking through controls and flows and reading the code behind them, again without screenshots. Choose Looks and works fine to move on without a review. Reviews can use a lot of extra tokens, so they only run when you say yes. Leave this off to skip both the question and the review.

Smart game engine

toggle
default:"On"
Applies in the Game studio. Before building a new game, the AI picks the engine that suits it: Phaser for platformers, shooters and RPGs, Three.js for 3D games, and no engine for simple arcade, puzzle and card games, which then load faster. If you name an engine in your prompt, your choice always wins. The chat shows which engine was picked, right after the AI’s first sentence. Turn it off to let the builder choose as it writes. See Game engines.

Smart website add-ons

toggle
default:"On"
Applies in the Website studio. Before building a new website, the AI picks ready-made libraries that suit it: Swiper for carousels, GLightbox for full-screen photos, GSAP or AOS for scroll animations, Lenis for smooth scrolling, Alpine.js for tabs and toggles, Chart.js for charts and Leaflet for maps. Simple sites get none, so they load faster. If you name a library in your prompt, your choice always wins. The chat shows which add-ons were picked, right after the AI’s first sentence. Turn it off to build new websites with plain JavaScript only. See Website add-ons.

Connectors

Connectors link outside services to your projects, so the AI wires them into what it builds. Click a card to set that service up. Each service’s page has an Enable switch, a box for its key, code or link (Pollinations has a sign-in instead), a How it works button, and Prompts to try: ready-made requests to copy into the builder chat. Changes save as you type. See Connectors for step-by-step setup of each service. The Surge card is the account Publish to the web uses. Its badge shows Connected when you’re signed in. Click it to sign in or create a free Surge account without publishing anything, or, when you’re signed in, to see your Surge email and click Sign out.
toggle
default:"Off"
Emails your form entries to you. Needs your Web3Forms access key. See Web3Forms.
toggle
default:"Off"
Counts visitors. Needs your Umami tracking code or website ID. See Umami.
toggle
default:"Off"
Counts visitors. Needs your Plausible tracking code. See Plausible.
toggle
default:"Off"
Adds a live chat bubble. Needs your tawk.to widget code. See tawk.to.
toggle
default:"Off"
Takes payments. Needs one or more Square payment links. See Square.
toggle
default:"Off"
AI images and AI features. Needs a sign-in with your Pollinations account. Under AI features in your sites, choose whether visitors pay with their own Pollen or your site key pays. See Pollinations.
toggle
default:"Off"
Search free stock photos and add them to the open project’s My images. Needs your free Pixabay API key: paste it and click Save key. The key stays inside AppBlips; click Remove key to forget it. See Pixabay.
toggle
default:"Off"
Lets the AI search the web while it builds and edits your projects. Needs your free Tavily API key: paste it and click Save key. Each search uses one Tavily credit. The key stays inside AppBlips; click Remove key to forget it. See Tavily.
React Bits shows Coming soon and can’t be opened yet. Missing a service? Click Request a connector at the end of the cards.

Tools

Tools are built into AppBlips: they need no outside service, account or key. Each card shows On or Off; click one to open its page, with an Enable switch, a How it works button and Prompts to try. See Tools.
toggle
default:"Off"
Built into AppBlips (beta). Turn it on so the AI can use your images; while it is off the AI ignores your images. Below the switch is the picture gallery of the project you have open, where you upload your own photos and logos for the AI to use. Click the eye on an image to hide just that one from the AI. With Pixabay set up, Find free photos on Pixabay searches free photos to add. See Using your own images.
toggle
default:"Off"
Built into AppBlips, with nothing to sign up for. Set separately for each project: it is off until you turn it on in that project, and can’t be used with no project open. Opens a short set of questions about the project you have open in their own window, two or three per page, ending with Send now (the AI applies them straight away) or Maybe later (saved for when you ask). If you type your website address, it asks before scanning that page. Click Review answers to see or change them later. The AI applies good search-engine optimization once after you save or change them. See SEO.


Data

Where projects are stored on your device.
  • Export all apps: downloads every saved app, its version history and its saved app data as one backup file. Imported sites aren’t included: export each one as a .zip instead (see Export the project). Pictures you added with My images aren’t in the file either: an app restored from it lists them, but you’ll need to upload them again.
  • Import apps: adds apps from a backup file. An app you already have is replaced only if the backup’s copy is newer.
  • Projects folder: desktop app only. Shows where projects are saved. Click Change… to pick another folder. The browser version saves projects in your browser instead.
See Back up or move your projects for moving apps between computers.

About

The AppBlips logo, the version you’re running (and whether it’s the desktop app or the browser version), links to the AppBlips website and source code, a Report a bug link that opens a new issue on GitHub, and the copyright notice. Below them are the legal links and the open source licenses; click Legal or Licenses under the buttons to jump to either. Links to the Privacy Policy and the Terms of Service. Every button or link in Settings that leaves AppBlips for another website first asks if that’s okay. The prompt names the website and says why it’s needed. Click Continue to open it in your web browser, or Cancel to stay.

Licenses

Credits for the open source code inside AppBlips.
  • AppBlips: AppBlips itself is open source under the MIT License. Click Show license to read it, or Source code to open the project on GitHub.
  • Open source packages: every open source package that ships inside AppBlips, with its version and license. Click a package to read its full license text and open its website. Type in Search packages to find one by name, license or author.
  • Other credits: the Whisper speech model that voice input uses, React Bits (whose component list AppBlips includes for the upcoming React Bits connector; click it to read its licence), the fonts in the interface, Surge (the hosting service Publish uses; no Surge code is included), and, in the desktop app, Chromium. Chromium’s own list of licenses is in the file LICENSES.chromium.html in the AppBlips install folder.

Danger Zone

These actions are permanent and cannot be undone.
  • Delete all saved apps: removes every saved app with its version history.
  • Reset app to factory defaults (the Factory Reset button): clears all data, settings, API keys and projects, signs you out of Surge and Pollinations, removes your Pixabay key, and returns AppBlips to the state it was in when you first installed it.