Skip to main content
This page explains where to get help with Lovable, what the support team covers, and what to expect on each plan.
  • Everyone can use the docs, the docs assistant, the status page, and the community on Discord.
  • Paid plans add direct help from the support team.
  • Enterprise plans add a dedicated account team.

Get help fast

You usually solve a problem faster through self-help than through a support request. Start with the row that matches your situation.

What support covers

The support team helps with the Lovable platform and your account, including:
  • Billing issues, including refunds and unexpected charges
  • Platform bugs
  • Account management
  • Workarounds or solutions to known issues
  • General guidance on using Lovable
  • General questions about Lovable
The support team does not cover the following requests. Use the alternative listed with each one instead.
  • Project-specific debugging. The support team cannot debug the code in your project. Ask Lovable in chat, follow the debugging guide, or ask the community on Discord.
  • Implementing third-party or open-source integrations. If a connector from the catalog is not working as expected, start with its page in the connector catalog. For a service you integrated yourself, refer to that service’s own documentation.
  • Takedowns, abuse reports, and appeals. If your project was taken down or your account was disabled, the Trust & Safety team handles it through the forms at lovable.dev/abuse, not the support form. See If your project was taken down.
Other requests belong to another team or company, for example security vulnerabilities, privacy requests, or sales. See Not covered by support? Where to go.

Support by plan

What you can expect from support depends on your plan. The support team responds within 24 hours, mainly on weekdays. That is the time to a first reply, not the time to a resolution. On Enterprise plans, your contract and your account team set what response times to expect. See Enterprise support. For the full plan comparison, see Subscription plans.

Contact support

To use the support form, you need to be signed in, and your current workspace needs to be on a paid plan. On the Free plan, the Contact us button opens an upgrade prompt instead of the form.
1

Open the support form

Go to lovable.dev/support and click Contact us. Use the Lovable account that belongs to your paying workspace.
2

Describe the problem

Fill in the Subject and Message. Optionally select a Project so its URL is included in the request.You can attach images, PDF files, and DOC files, up to 5 MB in total.
3

Read the AI reply

Lovable’s support AI replies within a couple of minutes and resolves most questions.If the answer does not help, ask for a human. A member of the support team then follows up by email.
If the form is unavailable, email support@lovable.dev from the same account email.

What to include

The support team can start on your request immediately when your first message includes:
  • What you expected to happen, and what happened instead
  • The project URL, if the issue is tied to one project
  • Screenshots or a short recording of the problem
  • When it started, and whether anything changed shortly before
  • What you have already tried

Enterprise support

Enterprise plans add support and services beyond the product itself:
  • A dedicated account team as your single point of contact for onboarding, growth, and escalations
  • Priority response times
  • Comprehensive onboarding and ongoing training
For everything the Enterprise plan includes, see Lovable for Enterprise.

Buy or upgrade to Enterprise

To buy an Enterprise plan, or to move an existing workspace to Enterprise, contact sales. The sales team handles pricing and contract questions. Enterprise plans are arranged with the sales team, not through the support form.

Contact support from the editor

Enterprise workspaces can open a support request from inside a project, without using the support form. In the editor, click the + button next to the chat input to open the Chat actions menu, select Help & support → Contact support, and describe what is going wrong. This is one of the Enterprise support features. You can attach up to 5 JPG or PNG files, with a total size of 5 MB. Lovable attaches your project, workspace, and account details automatically, so the support team has the context without you filling anything in. The support team replies by email. Everyone with access to the project can use this option.

Response times on Enterprise plans

Your contract sets out the support terms for your organization, including how quickly Lovable responds. For questions about them, contact your account team. The general conditions are in Sections 10 and 11 of the Product Terms.

Not covered by support? Where to go

Some requests are handled by other teams or companies. Sending them to the support form only delays them.

If your project was taken down

Lovable blocks or removes projects that break the Platform Rules, for example:
  • Phishing or impersonation
  • Malware
  • Illegal goods or services
  • Adult content
  • Content that infringes someone else’s copyright or trademark
The Trust & Safety team makes these decisions and reviews appeals, not the support team. Use the appeal forms described below rather than the support form. What happens. You receive an email notification from Trust & Safety. Keep it, because the appeal forms refer to the steps in that notification. Depending on the case, Lovable blocks the project or removes it, and the published site is taken down. What you can do. If you believe the decision was a mistake, appeal at lovable.dev/abuse, signed in with the account that owns the project. Use the form that matches your notice. Trust & Safety does not process appeals filed on the wrong form.
  • Website Takedown Appeal, for a Platform Rules takedown.
  • Trademark Takedown Appeal, for a trademark complaint.
  • DMCA Counter-Notification, for a copyright complaint under the Digital Millennium Copyright Act (DMCA). If the complainant does not notify Lovable within 10 to 14 business days that they have filed a court action, Lovable restores the project. See the DMCA Copyright Policy.
  • Disabled Account Appeal, if your account was disabled.
Trust & Safety reviews every appeal and replies by email. Submitting an appeal does not guarantee reinstatement. To report a project built by someone else, use the report form at the same address.

FAQ

These are the questions the support team answers most often. Each answer gives the short version and links to the full one.

Billing and subscription

These entries cover canceling, invoices, refunds, message costs, and what happens when credits run out.
Go to Settings → Plans & credit usage, select Manage on your plan card, then Downgrade to free. Your plan stays active until the end of the current billing period. After that, your workspace moves to the Free plan.On a phone, cancel from lovable.dev in your browser. The mobile app has no cancel option.Plans bought inside the iOS app work differently. Each purchase covers one month and does not renew, so you have nothing to cancel.See Cancel your subscription.
Go to Settings → Plans & credit usage, select Manage on your plan card, then Invoices & payments. Lovable opens the Stripe billing portal.The portal lists your invoices, receipts, payment methods, and billing details. Stripe stores these on Lovable’s behalf, so the portal is the only place to view or change them.Enterprise workspaces billed under a contract do not use the billing portal. Ask your account team for invoices.See Manage billing, payment method, and invoices.
Subscription fees and credits are non-refundable, except where the law requires a refund. See the No Refunds section of the Terms of Service.If you believe you were charged in error, for example a subscription that renewed after you canceled, contact support with your workspace and the charge in question. The support team reviews billing errors.When you cancel, Lovable stops future charges but does not refund the current billing period. Your plan runs until the period ends, and unused credits are frozen rather than refunded. See Subscription plans.
Check your plan and subscription status in Settings → Plans & credit usage. You can also ask Lovable in chat whether your subscription has activated.If the plan still has not changed, contact support. See Troubleshooting on the Subscription plans page.
You cannot keep building until credits are available. Your published site stays live, and visitors can still open it.Two features stop working:
  • AI features inside deployed apps stop working.
  • Apps that use the built-in backend (Cloud) pause shortly after the balance reaches zero. The built-in backend is the database, login, and file storage Lovable runs for your app. While it is paused, the page still loads, but logins and data stop working.
Add credits, or enable auto top-up on Pro and Business plans. A paused backend does not resume by itself after a top-up. Open More → Cloud → Overview in the project and click Wake up. See What happens when you run out of credits.
Build mode is priced on the work Lovable does, not on the length of your message. A short request can cost more when Lovable has to explore the codebase, verify the result, check it in the browser, search the web, or generate images.To see what any message cost, open the More options menu below Lovable’s response and look under Credits used. For long messages, Lovable pauses and checks in with you when a single message passes your check-in level, 20 credits by default.Plan mode messages cost 1 credit each. See Build costs.
Your account includes 10 free fixes, shared across Try to fix on build errors and fixes from the Security view, in all your workspaces and projects. Each free fix becomes available again 24 hours after you use it.After you have used all 10, Try to fix still works, but it runs as a standard chat message and uses credits. See Fix errors and get unstuck.

Publishing and domains

These entries cover changes that do not appear on the live site, a site that is down, custom domains, and how your site appears in search results and link previews.
Publishing deploys a snapshot of your project. Lovable does not push later edits live on its own.To update the live site, click Publish, then Publish changes. A dot on the Publish button shows when you have changes waiting to be deployed.See Republish to make new changes live.
Check the status page first. If there is no incident, work through these checks:
  • Open the Publish dialog and confirm the project is still published.
  • If you use a custom domain, go to Project → Settings → Domains and check that its status is Live.
  • Ask Lovable in the project chat about the domain. It reports the domain’s state.
If everything looks right and the site still does not load, contact support with the project URL and what you see. See Hosting.
DNS is the system that points your domain name at a website. DNS changes can take up to 72 hours to reach every network. If you connected the domain recently, you may only need to wait.If your domain shows an old website, your DNS provider probably still has A, AAAA, or CNAME records from a previous host. These records tell the internet where your domain points. Remove them so that only Lovable’s records remain, then check the expected records in Project → Settings → Domains.Ask Lovable in chat about the domain. Lovable reports its state, which records it expects, and whether it can see them. See Troubleshooting domains from other providers.
Your app’s auth redirect URLs probably do not include the new domain yet. These are the addresses your app is allowed to send users back to after they sign in.Ask Lovable in chat to add the domain to the auth redirect URLs. See Site URL and redirect URLs.
Ask Lovable in chat. Lovable generates the site title, the meta description shown under it in search results, the favicon shown in browser tabs, and the social sharing image shown in link previews while it builds your app. Each page can have its own. To change any of them, describe the change in chat, for example a new site title or a new social sharing image for the pricing page.Metadata edits are standard chat messages and use credits. See Site metadata is generated for you.
Google indexing, which adds your pages to its search results, takes from a few hours to a few days after publishing, and sometimes longer. To speed it up, submit your sitemap in Google Search Console, use URL Inspection on important pages, and request indexing for new or updated pages.Run the review in your project’s SEO & AI search tab to check indexing, metadata, and sitemap issues on the live site. SEO stands for search engine optimization. See Optimize your app for SEO and AI search.

Cloud and your data

These entries cover a paused built-in backend, resuming after a top-up, taking your data with you, and sign-up emails that do not arrive.
The most common cause is a paused built-in backend (Cloud). The built-in backend is the database, login, and file storage Lovable runs for your app. The page still loads because the frontend is served separately, but the app cannot reach its data.Cloud pauses in three situations:
  • Your workspace has no credits left.
  • The project has been inactive for a period of time.
  • You paused it yourself.
Check your balance in Settings → Plans & credit usage. Then open More → Cloud → Overview in the project and click Wake up on the paused project card. See Pause Cloud.
A top-up does not resume a paused backend by itself. Visiting the deployed app or waiting does not resume it either.Open More → Cloud → Overview in the project and click Wake up.If the project still does not resume after you wake it up, contact support with the project URL. See Pause Cloud.
Yes. Export project data, under More → Cloud → Overview → Advanced settings, downloads your full database as a single file, an SQL (Structured Query Language) dump, that contains your tables and their data. You can run one export every 24 hours.The export does not include:
  • Files in storage buckets
  • Edge function code, the server-side code Lovable runs for your app
  • Your project’s secrets
  • User passwords in a usable form, so plan a password reset for migrated users
You cannot export while the backend is paused, so resume it first. See Export Lovable Cloud data and Deploying and hosting outside Lovable.Your code is separate from your data. On paid plans, you can take a copy of the code with Download codebase in the code editor. On any plan, you can keep a repository in sync with Git sync.
Ask your users to check their spam folder first. Email providers often filter messages from new domains there.If many people sign up at once, your project may have reached its hourly email sending limit. For better deliverability and a branded sender address, set up custom emails. See Troubleshooting on the Email authentication page.

Code and GitHub

These entries cover connecting a repository, bringing in existing code, and downloading your project.
A workspace admin or owner first connects the workspace to GitHub. After that, workspace or project admins and owners can link a project from Project settings → Git → GitHub, or from Connectors → GitHub in the Chat actions menu, the + button next to the chat input.Linking creates a new GitHub repository for the project. The repository is private by default, and each project connects to one repository. See Link a project to a GitHub repository.
No. Git sync exports from Lovable, and connecting a project creates a new repository. Lovable cannot start a project from code that already exists elsewhere. See Git sync.
On paid plans, anyone with edit access can save the whole project as a .zip file. Either click Download codebase at the bottom of the code editor’s file panel, or use the Download codebase section in Project settings → Git.To keep a repository in sync instead, set up Git sync with your Git provider. See Code editor.

Account

These entries cover signing in, changing your sign-in email, and deleting your account.
Sign in at lovable.dev/login with the same method you signed up with: email and password, Google, GitHub, Apple, or SSO. If you are not sure which method you used, enter your email on the login page and Lovable marks the linked method as Recommended.If you signed up with email and password, click Forgot password? on the login page to reset it. If you signed up with Google, GitHub, Apple, or SSO, there is no Lovable password to reset. Sign in with that provider, and reset your password with the provider if needed. See Sign in to an existing account and Reset your password.
Not directly. Create a new account with the email you want, then move your projects into it by remixing them.See Move a project to another account.
Go to Settings → Your account and select Delete account.Deletion finalizes after a 30-day grace period. During those 30 days, you can sign back in and cancel it. See Delete account.

Getting support

These entries cover response times, reaching a person on the support team, and what the team does and does not handle.
On paid plans, the support team responds within 24 hours, mainly on weekdays. That is the time to a first reply, not to a resolution. Business plans are prioritized for a faster response.On Enterprise plans, your contract and your account team set what response times to expect. See Enterprise support.
Yes. The first reply to a support request comes from Lovable’s support AI, which resolves most questions within a couple of minutes.If the answer does not help, ask for a human. A member of the support team then follows up by email.
The support form is available on paid plans. On the Free plan, you have three options:
  • The docs, and the docs assistant on every page of docs.lovable.dev
  • The docs assistant in the search box on lovable.dev/support
  • The community on Discord
No. The support team covers the Lovable platform and your account, not the code in your project.Ask Lovable in chat to investigate, use Try to fix on a build error, or revert to an earlier version. See Debug and fix errors.If you would rather have someone build it for you, browse Lovable experts.
No. Takedowns are handled by Trust & Safety, not the support team. Appeals go through the forms at lovable.dev/abuse.See If your project was taken down for which form to use and what to expect.