You built the app. It runs on localhost:5173. Now you want a real URL.
Hostinger gives you two ways to get a React app live. The first is a plain file upload that works on the cheaper shared plans. The second connects your GitHub repo and rebuilds the app every time you push, but it needs a Business or Cloud plan.
This guide covers both, plus fixes for the two problems people hit most: the 404 on refresh and the blank white page.

Which method should you use?
- Upload the build folder (File Manager). Works on any Hostinger shared plan. You build the app on your computer, then upload the files. Good if your app has no server code and you update it now and then.
- Node.js Web App from GitHub. Needs Business web hosting or a Cloud plan (Startup, Professional, Enterprise, or Enterprise Plus). Hostinger runs the build for you and redeploys on every push. Good if you update often or your app has a backend.
On a cheaper shared plan, use the first method. You don’t need to upgrade.
Before you start
You’ll need:
- A Hostinger hosting plan with a domain attached
- Your React project on your computer, with Node.js installed
- A GitHub account (Method 2 only)
Don’t have a plan yet? See current Hostinger plans
Method 1: upload your React build to Hostinger
React apps compile down to plain HTML, CSS, and JavaScript. That means any shared hosting plan can serve them. No Node.js needed on the server.
Step 1: build the app
Open a terminal in your project folder and run:
bash
npm run build
Vite puts the output in a folder called dist. Create React App uses build. Open that folder and you’ll see an index.html and an assets folder (or static).
Step 2: open File Manager in hPanel
Log in to hPanel, open Websites, click Manage on your site, then go to File Manager. Hostinger’s panel is called hPanel, and the labels move around now and then, so look for File Manager if your menu looks slightly different.

Step 3: clear public_html
Open the public_html folder. Hostinger puts a placeholder page in there. Delete it so it doesn’t load instead of your app.
Step 4: upload the contents of your build folder
Here’s where most beginners slip. Upload what’s inside dist (or build), not the folder itself. Your index.html has to sit directly in public_html.
The easiest way: zip the contents of dist, upload the zip into public_html, then use File Manager’s extract option. One upload beats dragging 40 files.

Step 5: add the routing rule (React Router only)
If your app has more than one page and uses React Router, refreshing a page like /pricing will throw a 404. The server looks for a file called pricing, finds nothing, and gives up.
Fix it with an .htaccess file. In File Manager, create a new file in public_html named .htaccess and paste this:
apache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.html$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.html [L]
</IfModule>
This sends every request that isn’t a real file back to index.html, and React Router takes it from there.
Step 6: test it
Open your domain. Click through a few pages. Then refresh on a page that isn’t the homepage. If that works, you’re done.
While you’re in hPanel, turn on the free SSL certificate so the site loads over https.
Method 2: deploy from GitHub with a Node.js Web App
Hostinger calls Node.js apps “Web Apps” in hPanel. This route needs a Business or Cloud plan, a package.json in your project, and Node.js 18, 20, 22, or 24. Hostinger detects React and Vite on its own.
Step 1: push your project to GitHub
Your code needs to live in a repo first. Leave out node_modules (a .gitignore handles that).
Step 2: start a new Node.js web app
In hPanel, open Websites, click Add Website, then pick Node.js web app.

Step 3: connect GitHub
Click Connect with GitHub. A popup asks you to install the Hostinger GitHub app and choose which repositories it can see. Pick the repo with your React app and click Deploy.
Step 4: check the deploy settings
Hostinger fills these in for you. Read them before you confirm:
- Framework preset: React, Create React App, or Vite
- Branch: the branch that triggers builds (usually
main) - Node.js version: 22 is the default
- Build command:
npm run build - Output directory:
distfor Vite,buildfor Create React App
If you use environment variables, add them here before the first build. More on that below.

Step 5: deploy and watch the build
Click Deploy. The build log streams live. When it finishes, your app is up. From now on, every push to the connected branch rebuilds the site automatically.
Prefer to upload a zip instead of connecting GitHub?
Pick Upload your files in the same flow. Zip the project and leave out node_modules and .git:
bash
zip -r myapp.zip . --exclude "node_modules/*" --exclude ".git/*"
If your domain is already added to the plan as a regular website, remove that website first. The Node.js flow wants to create a fresh slot for the domain.
One catch: Hostinger generates an .htaccess file for you on every deploy and overwrites hand edits. So the routing rule from Method 1 won’t stick here. If refreshing a route gives you a 404, use Method 1 instead, or ask Hostinger support how they handle single-page app routing on your plan.
Fix the common problems
Blank white page. Open your browser’s developer console. If you see 404 errors for your JavaScript files, the app is looking for them in the wrong place. In Vite, check the base option in vite.config.js. In Create React App, check homepage in package.json. For an app at the root of your domain, you usually want neither set.
404 when you refresh a page. Add the .htaccess rule from Method 1, step 5.
Environment variables not working. React bakes them into the app at build time. Vite only exposes variables that start with VITE_. Create React App needs REACT_APP_. On Method 1, they come from your computer at build time. On Method 2, add them in the deploy settings before building. And remember that anything in a React env variable ends up readable in the browser, so never put a secret key there.
Build failed. Open the failed deployment and read the log. Hostinger also writes an automatic analysis of the failure. The usual causes are a wrong build command, a wrong output directory, or a Node.js version your dependencies don’t like.
403 after a redeploy. The .htaccess is stale or got edited by hand. Redeploy and Hostinger regenerates it.
How to update your app later
On Method 1, run npm run build again, then upload the new files and replace the old ones. Clear your browser cache if you still see the old version.
On Method 2, push to your connected branch. That’s it.
FAQs
Does Hostinger support React? Yes. You can upload a static React build to any shared plan, or run it as a Node.js Web App on Business and Cloud plans.
Do I need Node.js hosting to host a React app? Only if you want Hostinger to build the app for you or run server code like Express. A plain React front end runs fine from uploaded files.
Can I deploy Next.js on Hostinger? A static Next.js export works like any other static site. Server rendering needs the Node.js Web App route on a Business or Cloud plan.
Can I use my own domain? Yes. Point the domain to Hostinger, then attach it to your site in hPanel.
Which one should you pick?
If you’re starting out, go with Method 1. It takes about 10 minutes and costs nothing extra. Move to GitHub deploys once you’re pushing updates every week and rebuilding by hand starts to annoy you.
Ready to put your app online? Get started with Hostinger
Related reading: how to move a website from localhost to Hostinger


Pingback: Host a Node.js app on Hostinger: plans and steps (2026)