How to Use Base44: The Beginner's Guide (First Prompt, First App, Credits, and Publish)

CodexFuse Team · 2026-10-30T09:12:04.014Z · 13 min read

Base44 turns plain-language prompts into complete working apps. This beginner's guide covers account setup, credits, the first prompt, Plan Mode, testing, the security scan, and publishing.

Base44 is an AI app builder that turns plain-language prompts into complete, working web apps — no coding required. If you want to learn how to use Base44, the path is the same for everyone: create an account, write a clear first prompt, review the build, test it like a real user, then publish it. This beginner's guide walks that whole path in one place, from your first sign-in to your first app on your own domain. If you are comparing builders before you commit, our Lovable beginner guide covers Base44's closest rival side by side.

Everything below reflects Base44 as it works in late 2026, with pricing and credit limits checked against Base44's own site on October 30, 2026. Pricing moves, so treat any number here as current-as-of that date.

What is Base44?

Base44 is a no-code AI app builder that converts a plain-language description into a complete, working web app: the interface, the database, user accounts, payments, and the hosting it runs on. You type what you want in a chat box; Base44 generates the whole thing on real production infrastructure, not a sandbox demo. The popular name for this style of building is "vibe coding": the AI handles the coding while you bring the vision and judge the result. Base44 is now part of Wix, and its signature difference from rivals is that the backend is built in from the start — database, authentication, integrations — instead of something you wire up separately. The idea is catching on: in a 2026 survey of 1,000 U.S. adults, 57% had heard of vibe coding, though only 13% had ever tried it (All About Cookies).

Is Base44 free? How do the credits actually work?

Yes — Base44 has a genuinely usable free plan, but the currency you must understand is credits. Every prompt you send to the builder spends one message credit. Integrations with outside tools spend integration credits. Here are the plans as listed on base44.com on October 30, 2026 (annual billing shown):

Do the math before you start. On the Free plan, 25 message credits a month means every prompt counts: batch three fixes into one message instead of sending three separate ones. For context, one experienced builder used roughly 150 prompts to build a two-day budgeting app (All About Cookies, September 2026) — so the Free plan covers a small app or a landing page per month, while the $40/month Builder plan is the realistic entry point for anything with real users. Custom domains unlock at Builder level; Free and Starter projects live on a Base44 subdomain.

How do you set up a Base44 account?

Setting up takes about two minutes, and no credit card is needed for the free tier.

1. Go to base44.com and click Get Started.
2. Sign up with your Google account or an email address (email adds a quick confirmation step).
3. Pick your starting plan: Free if you are exploring, Builder if you already know you are building something real with users and a custom domain.
4. Use a modern browser — Chrome, Firefox, Safari, or Edge. Privacy-focused browsers can cause odd issues mid-build.

Once you are in, you land on the Base44 dashboard: a big prompt box, a templates gallery underneath, and a left menu with search, a super agent, and the apps you can connect. Start from a blank prompt or a template — templates are genuinely useful for a first build because they show what a good result looks like.

What should your first Base44 app be?

Pick something small but real: two to four connected features and one clearly defined user. Good first projects are a client portal for a freelance accountant, a staff scheduling tool for a small cafe, a hair-salon booking app, or a simple spending tracker. Avoid your dream app for now — a Salesforce-scale CRM is not a first project. Set expectations with this rough timing from experienced builders: a simple landing page can be done in a day, a moderately complex app like a budget tracker or scheduling tool takes two to four days of focused work, and anything with multiple user roles or third-party integrations can stretch to weeks (All About Cookies, September 2026). If your first goal is literally just a landing page, our AI landing page tool builds one in minutes — a good warm-up before the full app builder.

How do you write a first prompt that Base44 gets right?

Specificity is the whole game. Base44 fills in whatever you leave vague, and vague blanks produce a generic app that looks like a dozen others. Before you write, answer for yourself: who is it for, what problem does it solve, and what are the three or four core features? Then write your first prompt like a short product requirements document (PRD):

• Purpose in one line: "A booking app for a two-chair hair salon."
• Who uses it: "Clients book appointments; staff approve them."
• Core features: "Service list with prices, a calendar picker, client profiles, SMS-style reminders, a staff dashboard showing today's bookings."
• Key flows: "A client picks a service, picks a time, enters a name and phone number, and gets a confirmation. Staff see new requests and approve or reschedule them."
• What NOT to invent: "Don't invent staff names, prices, or salon details — use placeholders."

Then use Plan Mode: instead of building immediately, Base44 turns your description into a detailed blueprint — pages, data, user flows — and asks clarifying questions before it writes a line of code. Review and tweak the plan until it matches your intent, then let it execute. One important credit trick: on the Free plan, draft your PRD in ChatGPT or Claude first and paste the finished version into Base44 as your first prompt, so you don't spend your 25 monthly credits on planning. On Builder and above, Plan Mode inside Base44 is the better route because planning and execution stay seamless.

How do you turn the plan into your first app?

Paste your PRD into the chat box (or accept the Plan Mode blueprint) and send it. The initial build takes roughly 5 to 10 minutes depending on complexity — longer for detailed apps. When it finishes, resist the urge to immediately keep prompting. Your job now is to review version 1.0 with fresh eyes, because the AI built it and you don't yet know what's working, what's broken, or what's missing.

1. Check that everything you asked for exists. Click through the navigation and confirm each feature is there in some form. Missing something? Ask for it by name in the chat.
2. Check fonts and colors. From the dashboard, open Code, find index.css, and look for the font and color variables — Base44 pulls fonts from the Google Fonts library, so you can request any font by name in chat.
3. Fix the app name and logo quirk. Base44 keeps one name/logo inside the app and a different set in the dashboard, and they rarely match on their own. Click the app name at the top-left, choose App Overview, and set both to match.
4. Test every user role. Use the Acting As mode (three-dot menu in Preview > Act as a user) to see the app as an admin, a regular user, and a guest.
5. Test every screen size. Switch the preview to tablet and mobile views and re-run your flows — layouts that look perfect on desktop regularly break on phones.

Walk every major flow end to end: click every button, submit every form, try empty inputs and invalid entries. Nobody else is going to QA your app — Base44 has no automated end-to-end testing button, so you are the tester.

How do you fix problems without burning all your credits?

Fix efficiently: one prompt, several fixes. Describe what you did, what you expected, and what actually happened — Base44 usually nails the fix on the first try when the bug report is complete. For visual nits (a misaligned element, the wrong color), skip the chat and use the element isolator: click Edit at the bottom of the chat panel, click the element, and describe only how it should change. If a fix stalls after a few attempts, switch to Discuss Mode, where Base44 reads its own codebase and reasons about what's wrong before changing anything. And when something goes sideways mid-build, use the Revert button in the chatbox rather than arguing with the AI — save the Clone App feature for launched apps, where it works like a staging copy for testing big changes safely. Each builder has its own prompting rhythm; our Bolt beginner guide shows how the other leading prompt-to-app tool handles the same iterate-and-fix loop.

What are Skills, and should a beginner use them?

Skills are saved guidelines that automatically shape how Base44 builds your app, so you stop repeating the same preferences in every prompt. Base44 ships with pre-built ones for accessibility, UI/UX rules, and marketing copy — turn on the accessibility Skill and your app follows WCAG 2.1 standards without you thinking about it. Add your Skills right after you finish planning (Step 2 above) so the first build already incorporates them. This is one of the two power features beginners usually discover months late; the other is Clone App.

How do you run Base44's security scan?

Run it before you publish — it's the most valuable built-in feature for a non-technical builder. Security is exactly where "you don't know what you don't know" hurts, and the scanner flags issues in your codebase ranked by severity.

1. Click Dashboard at the top of the screen.
2. Select Security in the left-hand menu.
3. Click Run Security Scan in the top right.
4. Review the findings, then click Fix next to an issue — or Fix All to handle everything at once.

One caution from experienced builders: some fixes lock down capabilities you might want later. If a low-severity fix would restrict a feature you may add someday and you're not sure, skip it and revisit later.

How do you publish your Base44 app on your own domain?

Publishing is the finish line, and the custom-domain step comes first — otherwise your app lives on a yourapp.base44.app subdomain.

1. From the dashboard, click Dashboard in the top-left menu, then Domains.
2. Buy a new domain, connect one you already own, or pick one of Base44's suggestions.
3. Click Publish in the top right and choose your visibility: the default is public but login-required, meaning anyone can visit but must create an account to use the app.
4. Confirm the Edit URL field shows your custom domain, then click Publish App.
5. Share it from the pop-up (Facebook, LinkedIn, X, WhatsApp, Reddit) or come back to the Publish button any time for the share links.

Remember: connecting a custom domain requires the Builder plan or higher. On Free or Starter, publish to the Base44 subdomain and upgrade when the app earns its keep.

Base44 vs Lovable vs Bolt: which should a beginner pick?

All three turn prompts into apps, but they differ where beginners feel it most: the backend.

The short version: if you want one platform that handles the database, logins, and hosting without you touching them, Base44 is the simplest start. Our Replit beginner guide covers the agent-based alternative for builders who want to see and steer the code more directly.

Sources

• All About Cookies, "How To Start Vibe Coding With Base44: A Beginner's Guide to Building Your First App" — article updated September 10, 2026 (7-step walkthrough: plans, PRD/Plan Mode, first build review, user-flow testing, security scan, custom domain and publishing; credit-usage figures; Skills and Clone App features). https://allaboutcookies.org/how-to-start-vibe-coding-with-base44
• Base44 official pricing page — checked live October 30, 2026 (Free/Starter/Builder/Pro/Elite prices and credit allowances; "you own your code, data, and users" with two-way GitHub sync; every plan includes AI building, integrated backend and database, analytics). https://base44.com/pricing
• A1 Republic, "How To Make Money With Base44" — published October 2026 (beginner dashboard tour: prompt box, templates, left menu with super agent and connected apps; Build mode with setup questions; plan-limit warnings before publishing). https://a1republic.com/blog/base44-make-money
• B12 AI directory, "Base44 – AI App Builder" — checked October 2026 (free plan 25 message credits/month; all-in-one approach with built-in hosting, database, and auth vs. Lovable). https://www.b12.io/ai-directory/base44/
• Emvigotech, "Step by Step Guide to Building an App in Base44" — published 2026 (account setup with no credit card required, Builder Chat flow, template starting points). https://emvigotech.com/blog/base44-app-development-guide/

Frequently asked questions

Can I really build an app with Base44 if I have never coded?

Yes — that is the entire point of the product. You describe the app in plain language and Base44 builds the interface, database, logins, and hosting. The skills you need are clarity and patience: a specific prompt, a reviewed plan, and thorough testing of the result. No programming knowledge is required at any step.

Is Base44 actually free, or will I hit a paywall?

The Free plan is real: $0, with 25 message credits and 100 integration credits per month and up to 5 apps, including auth, database, and analytics. You will hit the credit limit if you iterate heavily — each prompt costs one credit — and custom domains require the $40/month Builder plan. Start free, upgrade when the app justifies it.

Do I own the app and the code I build on Base44?

Yes. Base44 states that you own everything you build — your code, your data, your users — and two-way GitHub sync exports the full source code to your own repository at any time. Nothing is locked to the platform.

Can I sell the app I build on Base44?

You own what you build, so yes — many people build client portals, booking systems, and dashboards for paying customers. Just check your plan's usage limits before publishing for paying users, never promise features you haven't tested, and get professional review if the app handles regulated data like health or finance records.

Can I publish my Base44 app to the App Store and Google Play?

Base44 has a built-in workflow that checks your app against each store's guidelines and prepares the submission files. You still need your own developer accounts — $99/year for Apple and a $25 one-time fee for Google Play — but the technical side is handled for you.