cPanel gives you three main ways to create a website: the built-in Sitejet site builder for a no-code design, the WP Toolkit to install WordPress in a couple of clicks, or the File Manager and FTP to upload your own HTML or application files. Which one you pick depends on what you are building, and it is worth knowing all three plus the point where a modern repo-based deploy fits the job better than the cPanel workflow.
cPanel is still how a huge share of the web gets published, and it is genuinely capable. Knowing its three paths - and their ceiling - saves you fighting the wrong tool.
Table of contents
- Option one: the site builder
- Option two: WordPress via WP Toolkit
- Option three: upload your own files
- Where the cPanel model shows its age
- Where RunxBuild fits
- FAQ
Option one: the site builder
Modern cPanel includes the Sitejet Builder, a drag-and-drop website builder reachable from the Domains section. You pick a template, edit it visually, and publish it directly to your domain - no code, no separate hosting setup. It includes templates, an AI text generator, and full access to the underlying code if you want it.
This is the fastest path for a brochure or small business site where you want a designed result without writing HTML. It lives inside cPanel, so the site you build is served by the same hosting account, with the domain and SSL already wired up. For a non-technical owner who just needs a presentable site, this is often the right call.
Option two: WordPress via WP Toolkit
If you want a CMS - a blog, a content-heavy site, something with plugins - cPanel’s WP Toolkit installs WordPress for you. You give it a site title and admin details, and it provisions the database, installs WordPress, and hands you a working admin panel. The Onboarding Assistant can even do this automatically when a new account is created with the WordPress option.
WP Toolkit then manages updates, staging, and security hardening from one screen. This is the standard path for the enormous number of sites that run on WordPress, and it removes the manual download-database-config dance that used to be the first hour of any WordPress install.
Option three: upload your own files
For a hand-built site or a custom application, the File Manager and FTP let you upload files directly into the public web root (usually public_html). Drop your HTML, CSS, and assets there and they are served immediately. For apps that need a runtime, the Application Manager can run Node or Python through Passenger, within the limits of the shared environment.
This is the most flexible cPanel path and also the most manual - you are responsible for the file layout, any build step, and keeping the uploaded version in sync with your source. It works, and it is exactly the friction that repo-based deployment was invented to remove.
Where the cPanel model shows its age
cPanel’s model is a server you log into and manage: files in a web root, a control panel for everything, manual uploads or a builder. For a static site or WordPress, that is fine. For a modern application, it starts to chafe - there is no clean tie between your Git repository and what is live, deploys are a manual upload or an FTP sync, and rolling back a bad change means restoring files by hand.
The newer model connects a repository to the host so that pushing code is the deploy, with build logs and one-click rollback. Neither is wrong; they suit different work. The signal to move is when manual uploads and no deploy history start costing you real time.
Where RunxBuild fits
For the application case, RunxBuild replaces the upload-and-manage loop with a repo connection: you deploy a static site or a Node, Python, Go, Ruby, Java, or Docker service straight from GitHub, with build logs, a live route, environment variables, and rollback to a previous deploy. For WordPress, there is a managed WordPress plan with a file manager and a database browser in the dashboard, so you get cPanel’s convenience features without SFTP or phpMyAdmin.
So if cPanel’s site builder or WP Toolkit fits your project, they are reasonable. When the project is an app that wants a Git-based deploy and a rollback button, that is the workflow RunxBuild is built around.
How this fits the rest of the stack
The cost of a project is the sum of its line items, not the headline number, and the RunxBuild hosting calculator is the right place to add them up: the service, the database, the storage, the bandwidth, each a separate figure. Model it before committing, not after the first invoice. The RunxBuild dashboard is where the running project shows its real usage in one place.
Useful related references:
FAQ
How do I create a website in cPanel?
Three ways: use the built-in Sitejet Builder for a no-code drag-and-drop site, install WordPress through WP Toolkit for a CMS, or upload your own HTML or application files via File Manager or FTP into the public_html web root. The right one depends on whether you want a builder, a CMS, or full control.
Can I install WordPress from cPanel?
Yes. cPanel’s WP Toolkit installs WordPress in a couple of clicks - it provisions the database, installs the software, and gives you the admin panel, then manages updates, staging, and hardening from one screen, removing the manual setup WordPress used to require.
Where do I upload my website files in cPanel?
Into the public web root, usually the public_html directory, using the File Manager or an FTP client. Files placed there are served on your domain immediately. Applications that need a runtime can use the Application Manager to run Node or Python through Passenger.
Is cPanel outdated for modern web apps?
For static sites and WordPress it is still fine. For modern applications its manual upload-and-manage model lacks a clean Git-to-live deploy, build logs, and easy rollback. A repo-based platform where pushing code is the deploy fits application work better, which is the usual reason teams move.
What is the alternative to cPanel for deploying an app?
A repo-based platform that connects to your GitHub repository and deploys on every push, with build logs, a live route, and one-click rollback, rather than manual FTP uploads. For WordPress specifically, a managed WordPress plan with a dashboard file manager and database browser offers cPanel’s conveniences without the server-login workflow.