If you’re currently on a different plan, you can upgrade<\/a> your hosting plan through hPanel to access Node.js support.<\/p> Your Node.js app must be built with one of these frameworks:<\/p> Supported Node.js versions:<\/strong> 18.x, 20.x, 22.x, 24.x<\/p> In addition to the listed frameworks, Hostinger also supports an “Other”<\/b> type for Node.js applications that don’t use a specific detectable framework.<\/p> Log in to your Hostinger hPanel<\/strong>, navigate to Websites<\/strong> on the sidebar, and click Add Website<\/strong>:<\/p> Choose Node.js Apps <\/strong>from the available options.<\/p> Select Import Git Repository<\/strong>:<\/p> You’ll be redirected to GitHub. Click Authorize<\/strong> to allow Hostinger to access your repositories:<\/p> Choose the repository containing your Node.js app:<\/p> The system will automatically detect your framework and suggest build settings where you can modify them.<\/p> If your framework type is “Other”:<\/b><\/p> When “Other”<\/b> is selected, Hostinger’s detection script will try to gather as much configuration information as possible. However, some settings may need to be filled in manually:<\/p> If you’re unsure of these values, check your project’s Click Deploy<\/strong> to start building your application.<\/p> Your Node.js app is now live! 🚀<\/p> Once the deployment is complete, you will see a preview screenshot of your built website. This gives you a quick visual confirmation that the deployment was successful before navigating to your site.<\/p> Log in to hPanel<\/strong>, go to Websites<\/strong>, and click Add Website<\/strong>:<\/p> Choose Node.js Apps from the options.<\/p> Select Upload your website files<\/strong>:<\/p> Upload a compressed file ( Confirm or edit the auto-detected build settings:<\/p> If your framework type is “Other”:<\/b><\/p> When “Other”<\/b> is selected, Hostinger’s detection script will try to gather as much configuration information as possible. However, some settings may need to be filled in manually:<\/p> If you’re unsure of these values, check your project’s Click Deploy<\/strong> to build and launch your application:<\/p> Your website is now ready to use!<\/p> Once the deployment is complete, you will see a preview screenshot of your built website. This gives you a quick visual confirmation that the deployment was successful before navigating to your site.<\/p> The Node.js Website Dashboard has features to help you quickly access important information:<\/p> 1. GitHub Repository Quick Link<\/b> 2. Last Deployment Details<\/b> 3. Quick Links to Key Features<\/b> 4. Resource Usage Graphs<\/b> 5. Restart<\/strong><\/p> The dashboard includes a Restart<\/strong> button when you click Running<\/strong> for server-side Node.js applications. Use this to restart the server process directly from hPanel — no full rebuild or redeployment needed.<\/p> For Node.js applications that generate back-end build files (e.g., Express.js, Next.js, Nuxt.js, NestJS), build output is stored outside<\/b> of • Build files location:<\/b> If your application was previously deployed with build files inside 1. I already have a domain added at Hostinger. How do I deploy Node.js to it?<\/strong><\/p> Currently, Node.js websites must be deployed as a new website. Here’s the process:<\/p>What You’ll Need<\/h2>
\n
Supported Frameworks and Technologies<\/h2>
\n
\n
\n
\n
\n
Deploying from a GitHub Repository<\/h2>
Step 1 – Access the Node.js Web App section<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/01\/2026-01-30_10-24_3.png\")
<\/p>Step 2 – Select Node.js Web App<\/h3>
Step 3 – Choose GitHub Integration<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/11\/2025-11-07_15-28.png\")
<\/p>Step 4 – Authorize GitHub Access<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/11\/c74d3095-697c-4f8f-9d5e-91973cbc76bf.png\")
<\/p>Step 5 – Select Your Repository<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/11\/f7e9bb52-0ab3-4547-9d68-267e8dbdded4.png\")
<\/p>Step 6 – Configure Build Settings<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/02\/2026-02-06_10-08.png\")
<\/p>\n
dist<\/code>, build<\/code>, out<\/code>, or .next<\/code>.<\/li>\nindex.js<\/code>, server.js<\/code>). This is only required if your application needs it.<\/li>\n<\/ul>![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/03\/2026-03-31_09-16.png\")
<\/p>package.json<\/code> or build configuration file.<\/p>Step 7 – Deploy Your Website<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/11\/38a2eb0d-a1ef-419e-a908-3e873ed6e031.png\")
<\/p>![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/04\/2026-04-13_18-32.png\")
<\/p>Deploying by Uploading Files<\/h2>
Step 1 – Access the Node.js Apps Section<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/12\/2025-12-23_13-28.png\")
<\/p>Step 2 – Select Front-End Application<\/h3>
Step 3 – Choose File Upload<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/11\/2025-11-07_15-28_1.png\")
<\/p>Step 4 – Upload Your Project<\/h3>
.zip<\/code>) containing your Node.js app.<\/p>Step 5 – Configure Build Settings<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/02\/2026-02-06_10-13.png\")
<\/p>\n
dist<\/code>, build<\/code>, out<\/code>, or .next<\/code>.<\/li>\nindex.js<\/code>, server.js<\/code>). This is only required if your application needs it.<\/li>\n<\/ul><\/p>package.json<\/code> or build configuration file.<\/p>Step 6 – Deploy Your Website<\/h3>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2025\/11\/39d8457e-b666-4c8b-9761-f5d95b259cad.png\")
<\/p>Managing Your Node.js App<\/h2>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/04\/2026-04-09_17-12.png\")
<\/p>
\nIf your app is deployed via GitHub, the dashboard now shows a direct link to the connected GitHub repository. Click it to open the repo in a new tab — useful for quickly checking your code, branches, or recent commits without leaving hPanel.<\/p>
\nThe dashboard now displays detailed information about your most recent deployment, including:
\n• Deployment status (success or failed)
\n• Timestamp of the last deployment
\n• A quick link to view the full deployment log
\nThis replaces the need to navigate to the Deployments section just to check the latest build status.<\/p>
\nNew quick navigation links have been added to the dashboard so you can jump directly to:
\n• Deployments
\n• Environment Variables
\n• Settings & Redeploy
\n• File Manager<\/p>
\nThe dashboard now includes average resource usage graphs for the most important plan limits, including CPU, RAM, and I\/O. These graphs give you a quick visual overview of how your Node.js app is consuming hosting resources — without needing to navigate to the full Resource Usage section.
\nIf any metric approaches the red dotted line (your plan’s limit), consider optimizing your app or upgrading your plan.<\/p>File structure after deployment<\/b><\/h3>
public_html<\/code>:<\/p>\/home\/{username}\/domains\/{domain}\/nodejs<\/code>
\n• .htaccess<\/code> location:<\/b> \/home\/{username}\/domains\/{domain}\/public_html\/.htaccess<\/code> — automatically created to handle routing and serve content correctly.<\/p>public_html<\/code>, they will be moved automatically on the next build.<\/p>
\n• This change applies to back-end frameworks only. Front-end-only apps (React, Vue, Angular) are not affected.
\n• If you encounter a 403 error after redeployment, check that the .htaccess<\/code> file in public_html<\/code> is correctly routing to the nodejs<\/code> directory. Redeploying the application regenerates this file.<\/div>Frequently Asked Questions<\/h2>
\n
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/01\/2026-01-05_15-17.png\")
<\/p>