What a static website is
A static website is made only of files: HTML pages, CSS for the design, JavaScript for anything interactive, and images, fonts and videos. When a visitor opens a page, the server sends the file exactly as it is stored. Nothing runs on the server first: no PHP, no database query, no application.
That covers far more sites than people expect. A company profile with five pages, a portfolio, a landing page for an ad campaign, a wedding or event page, product documentation, a resume site, a template bought from ThemeForest, or a site exported from a design tool are all static. So is the output of modern front-end tools: when you run npm run build in a React, Vue, Svelte, Angular, Astro, Hugo, Jekyll or Eleventy project, the result is a folder of static files.
When static is the right choice, and when it is not
Choose static hosting when your pages are the same for every visitor and you edit them on your own computer. You get the fastest possible pages, almost nothing that can be hacked, and no updates to install, because there is no CMS, plugin or PHP version to keep current.
- Good fit: brochure and portfolio sites, landing pages, documentation, a React or Vue app that talks to an API hosted elsewhere, sites built with Hugo, Astro or Jekyll.
- Not a fit: anything with logins, a shopping cart, a database or a contact form that sends email from your own server. Those need server code: WordPress or WooCommerce for most businesses, PHP for a custom site, or Node.js, Python or Java for an app.
- In between: a static site can still have a contact form through a form service, comments through an embedded widget, and search through a JavaScript library. Many businesses never need more.
Why not just use a PHP or WordPress plan?
You can host HTML files on almost any plan, and many people do. The difference is what else is switched on. A PHP plan runs PHP for every .php file, so an old script or a config file that ends up in the upload folder can run or be read. A static plan serves files only: on Cloud Ninza, PHP files, .env files, database dumps, backups and other code or config files are refused even if they are in your zip, so a mistake in what you upload cannot leak a password.
Static plans also come with a deploy flow made for files: one upload replaces the whole site in a single step and keeps the version it replaced. With a plain file manager you delete, upload and extract by hand, and for a few minutes the site can show a mix of old and new pages.
What static website hosting costs in India
Static plans on Cloud Ninza cost the same as the WordPress plans: Starter ₹149 a month, Growth ₹249, Business ₹349 and Pro ₹399, billed yearly (twelve months), and 2 years save 5%, 3 years save 10%, 4 years save 15% and 5 years save 20%. Every plan includes free SSL, free email accounts on your domain, off-site backups twice a day kept for 30 days, and support from engineers around the clock.
Free hosts such as GitHub Pages, Netlify and Cloudflare Pages are good for personal projects and open-source documentation. Businesses usually want email on their own domain, an invoice, servers in India, backups they can restore themselves, and someone to call when something breaks, which is where a paid plan earns its price.
Step 1: Get the folder right
Everything depends on one rule: the home page must be a file called index.html, at the top of the folder. Open your site folder and check that you see index.html next to folders such as css, js and images, not a single folder that contains all of them. (If your zip does have one folder at the top, Cloud Ninza notices and uses what is inside it.)
Check that links between pages are relative (about.html or /about.html, not file:///C:/Users/…), that image file names match exactly in upper and lower case (Logo.PNG and logo.png are different files on a server), and that nothing private is in the folder: no notes, exports or source files you would not want online.
- Windows: open the folder, select everything inside it (Ctrl+A), right-click → Send to → Compressed (zipped) folder.
- Mac: select everything inside the folder, right-click → Compress.
- A zip of the folder itself also works. Keep it under 100 MB; upload large videos separately with the File manager or SFTP.
Step 2: Choose a plan and an address
In the dashboard, open Launch an app, choose the Static website blueprint and a plan. Starter suits one site. Business and Pro hold several sites, for example a main site and a landing page for each campaign, each on its own domain.
If your domain is not ready yet, take a free cloudninza.in address: the site works on it straight away with HTTPS, and you connect your own domain later from the Domains page.
Step 3: Deploy the zip
Open Deploy a zip in the sidebar, choose the website and drop the zip onto the upload area. You see the upload progress, then a summary: how many files went live, and any warnings (for example PHP files that will not run on a static plan).
Behind the scenes the zip is unpacked into a new folder next to your site, checked, and then swapped in for the live site in one step. Visitors see the old site until the moment the new one is complete, never a half-copied mix.
Step 4: Point your domain and get HTTPS
Under Domains the dashboard shows the exact A records for your domain and checks, from public DNS, whether the domain already reaches the server. At the company that hosts your DNS, set the A record for @ and for www to that IP and remove any other A or AAAA records for those names.
As soon as the domain points to the server, a free Let's Encrypt certificate is issued automatically and HTTPS is switched on. If you use Cloudflare in front, set its SSL mode to Full or Full (strict), never Flexible.
Updating the site and undoing a mistake
To publish a new version, zip the folder again and upload it the same way. The Versions table under Deploy a zip lists the live version and the three before it; Make live switches back to an earlier one in seconds, and the version you leave is kept too.
For a one-line fix, the File manager is quicker: open public_html, edit the page and save. If you work with Git, connect your GitHub, GitLab or Bitbucket repository under Git deployments and every push goes live, with a build step for frameworks.
React, Vue, Angular, Astro and other builds
Run the build on your computer (npm run build), then zip the output folder: dist for Vite, Vue and Astro, build for Create React App, out for a Next.js static export, public for Hugo. Upload that zip, not the project's source code and never node_modules.
One detail matters for single-page apps. If the app uses client-side routes (React Router's BrowserRouter, Vue Router in history mode), refreshing a page such as /pricing asks the server for a file that does not exist. On a static plan, use hash routes (HashRouter, or createWebHashHistory in Vue), or host the build on a Node.js plan with the Static build preset, which answers every route with index.html. A Next.js app that uses server rendering or API routes is not static at all and needs a Node.js plan.
Small things that make a static site feel professional
A few details separate a site that works from one that feels finished:
- Clean addresses: on Cloud Ninza, /about serves about.html, so your links can leave out .html.
- Your own error page: add a 404.html at the top and it is shown for any missing page.
- Caching: browsers keep images and fonts for 7 days and CSS and JavaScript for an hour. After a design change, rename the file (style-v2.css) and update the link to make it show at once.
- A favicon, a page title and a meta description on every page, and an image for link previews (og:image) for WhatsApp and LinkedIn shares.
- Compress large images before uploading (WebP or AVIF where you can), because image weight decides how fast most static sites load.
Common problems and fixes
Almost every problem with a new static site is one of these:
- "There is no index.html": the home page is missing or inside a folder that holds other files too. Move index.html to the top and zip again.
- The design is missing (plain text page): the CSS link is wrong, often a capital letter or a file:/// path. Open the browser's developer tools (F12) → Console to see which file is not found.
- Images show on your computer but not online: check the exact file name, including upper and lower case.
- The old site still shows after a deploy: refresh the page (Ctrl+F5). If you use Cloudflare, purge its cache or wait a few minutes.
- A WAR file is refused: a WAR with servlets or JSP pages is a Java application and needs a Java plan, which runs it on Apache Tomcat.
Key takeaways
The short version, for anyone skimming:
- A static site is a folder of files with index.html at the top. No PHP, database or CMS runs, so it is fast and very hard to hack.
- On Cloud Ninza, choose a Static website plan (from ₹149 a month, billed yearly), zip the folder and drop it into Deploy a zip.
- Each upload replaces the site in one step and keeps the last 3 versions for one-click undo.
- React, Vue, Astro and Hugo sites are hosted as their build folder; apps that need server code need a PHP, Node.js, Python or Java plan.
- Free SSL is issued automatically once your domain's A records point to the server.
Static Website Hosting
Host an HTML, CSS and JavaScript website, or a React, Vue, Astro or Hugo build, on servers in India from ₹149 a month billed yearly. Backups twice a day (12 AM and 12 PM), last 30 days kept, restore any date yourself from your dashboard · Deploy a zip: upload a .zip, .tar.gz or a WAR of plain files and it goes live · Your last 3 versions kept, Make live to undo.
Hosting from ₹149 a month on servers in India
WordPress, static HTML, PHP, Node.js, Python and Java plans with free SSL and your choice of version. Create your account, pick a plan and pay by UPI, card or netbanking; your hosting is created automatically and you get your login by email, usually within minutes.