Move Your Lovable App to Your Own Hosting

Review the Project for External Deployment

Before moving the project, identify what needs to stay connected in production.

External Deployment Review

Identifies the backend, build settings, environment variables, and external services, then returns a short external-deployment checklist.

Review this Lovable project specifically for deployment outside Lovable. Identify: - whether the project is frontend-only or uses Lovable Cloud, Supabase, or another backend - the production build command and output directory - every environment variable required in production — names only - authentication or OAuth configuration that may need the production domain - external services such as Stripe, APIs, storage, email, or webhooks Do not change the project yet. Give me a short external-deployment checklist containing only what I need to configure after moving the frontend to another host.

Open Lovable

This guide moves the production frontend to Hostinger. Your existing Lovable Cloud or Supabase backend can stay connected.

Connect the Project to GitHub

Connect the project to GitHub so Hostinger can deploy it and receive future updates.

In Lovable:

Settings Connectors GitHub Connect project

Authorize GitHub, choose your account or organization, and connect the project.

The new repository contains your project files

The Lovable ↔ GitHub sync is active

IMPORTANT

Do not rename, move, or delete the connected repository while you still use Lovable sync.

Get Hostinger Web App Hosting

This workflow uses Hostinger to host the production version of your Lovable app.

Get Hostinger Web App Hosting

Deploy your Lovable project from GitHub and keep future updates connected.

USED IN THIS TUTORIAL

https://www.hostg.xyz/SHJyP

Already have Hostinger hosting? Continue below.

Import the Repository and Deploy

Then in Hostinger:

Websites Add Website Deploy Web App

Choose Import Git Repository Connect GitHub and select your Lovable repository Review the detected build settings Add the environment variables identified in Step 1 Deploy first to a temporary domain

For a standard Lovable project, Hostinger should normally detect the Vite setup. Lovable documents npm run build with dist/ as the standard build output.

Test the Temporary URL

Open the temporary URL and test the production version before connecting your real domain.

Main pages and routes

Page refreshes

Forms

Login and authentication

Database-connected features

Images and assets

External APIs or services

NOTE

If something that worked in Lovable no longer works, check the production environment variables first.

IMPORTANT

Do not connect the real domain until the temporary version works correctly.

Connect Your Production Domain

Connect your production domain from the Hostinger dashboard, then verify it.

The domain opens the app

HTTPS is active

Authentication still works

OAuth/redirect URLs use the production domain where required

Backend and external services remain connected

Continue editing normally in Lovable. Your workflow becomes Lovable → GitHub → Hostinger.

Changes synced to the deployed GitHub branch can trigger a new Hostinger deployment automatically, so you do not need to export and upload the project again each time.