LiveChat 
Support 
WHM Explained: What WebHost Manager Is and How It Differs From cPanel
If you have spent any time around web hosting, you have almost certainly bumped into the acronym WHM sitting right next to cPanel. They look alike, they sound related, and they are often mentioned in the same breath, which is exactly why so many people quietly mix them up. The good news is that once you see how they fit together, the confusion disappears for good.
WHM stands for WebHost Manager. It is the administrative control panel that sits *above* cPanel. Where cPanel hands one person the keys to manage a single website, WHM hands an administrator the keys to manage the *whole server* and to create, configure, and control all the individual cPanel accounts living on it. If cPanel is where you run your site, WHM is where you run the place that runs everybody’s sites.
This guide walks through exactly what WHM is, what you do with it, who actually uses it, and why it is the engine behind reseller hosting. By the end, the WHM-versus-cPanel question will feel obvious.
Key Takeaways
• WHM (WebHost Manager) is the admin-level control panel that sits above cPanel and manages an entire server.
• cPanel manages a single hosting account; WHM manages all of them, plus the server itself.
• WHM is used by server administrators and resellers — anyone responsible for more than one cPanel account.
• In WHM you create, suspend, and terminate cPanel accounts, build hosting packages, manage DNS, configure security, and handle SSL.
• Reseller hosting is built on WHM — it gives you the admin keys to create and brand cPanel accounts for your own customers.
• WHM is typically accessed on port 2087 (the secure login port).
What exactly is WHM (WebHost Manager)?
WHM is the back-office control panel for a hosting server. When a hosting company or a reseller provisions a server, WHM is the interface they log into to set it all up and keep it running. It controls the things that affect *every* account on the machine: how new accounts get created, what resources each one is allowed, how the server defends itself, and how email and DNS behave at the system level.
The cleanest way to picture WHM is as one half of a two-layer system. WHM is the upper, administrative layer. cPanel is the lower, end-user layer. They are made by the same company and built to work together, which is why the names travel as a pair. But they are aimed at two completely different jobs:
- WHM = “I manage the server and everyone’s accounts on it.”
- cPanel = “I manage my one website.”
When an administrator creates a new hosting account in WHM, what they are actually doing is spinning up a fresh cPanel account for someone else to use. So WHM is, in a very real sense, the cPanel *factory*. It produces and governs the cPanel accounts that end users eventually log into.
Here is the analogy that clears up the WHM-vs-cPanel confusion instantly: WHM is the landlord’s control panel, and cPanel is the tenant’s. WHM operates at the *building* level. It creates the apartments (each cPanel account), sets the lease terms (the hosting packages and resource limits), and controls building-wide systems like security, DNS, and shared resources. It is used by whoever *manages* the building — the admin or the reseller. cPanel operates at the *apartment* level: one tenant managing their own unit’s email, files, and databases, with no power over the building or the other tenants. So WHM and cPanel are not competitors or alternatives you choose between. They are two levels of the same system, and which one you use depends entirely on your role. If you are managing a whole server or reselling hosting to others, you live in WHM — the landlord’s office. If you are running your own single website, you live in cPanel — your apartment. This is also exactly why reseller hosting is built on WHM: it hands you the landlord’s keys so you can create and manage cPanel “apartments” to rent out under your own brand.
WHM vs cPanel: what is the real difference?
This is the heart of the matter, so let’s make it concrete. The single biggest distinction is level of access. WHM works at the server and account-administration level. cPanel works at the single-account, end-user level. Everything else flows from that one fact.
| Feature | WHM (WebHost Manager) | cPanel |
|---|---|---|
| Level | Server / administrator level | Single account / end-user level |
| Primary user | Server admins and resellers | Website owners |
| Main job | Manage the whole server and all accounts | Manage one website |
| Create accounts | Yes — creates cPanel accounts | No |
| Hosting packages | Defines packages and resource limits | Lives within an assigned package |
| Server security & firewall | Yes — server-wide controls | No |
| DNS management | Server-wide DNS and nameservers | DNS zone for the single domain |
| SSL | Installs and manages SSL across accounts | Manages SSL for the one site |
| Server-wide mail settings | Mailboxes for the one domain | |
| Default access port | 2087 | 2083 |
Notice how the two columns rarely overlap. A website owner in cPanel cannot create new accounts, cannot touch the firewall, and cannot change what resources their neighbors get — because those are *building-level* powers reserved for WHM. Meanwhile an administrator rarely fiddles with one site’s individual email filters in WHM, because that is an apartment-level chore handled inside cPanel.
Here is a second table that frames it by the question you should ask yourself:
| Your situation | The panel you use |
|---|---|
| I run one website and just need email, files, and a database | cPanel |
| I manage a server with many websites on it | WHM |
| I want to resell hosting to my own customers | WHM |
| I want to create new hosting accounts for clients | WHM |
| I need to suspend or terminate someone’s account | WHM |
Who actually uses WHM?
WHM is for anyone responsible for more than one hosting account. In practice, that lands in three camps:
- Server administrators. The people who run the hosting infrastructure — keeping the server secure, updated, and healthy, and provisioning accounts for everyone on it.
- Resellers. Individuals or businesses who buy hosting in bulk and sell it on to their own customers under their own brand. WHM is their command center. (More on this below, because it is the headline use case.)
- Anyone managing multiple cPanel accounts. Agencies, developers, and businesses that host several sites — perhaps for different clients or different brands — and want one place to create and oversee them all.
If you only ever touch your own single website, you will likely never open WHM, and that is completely fine. WHM is a tool for the *management* role, not the *occupant* role.
What do you actually do in WHM?
WHM packs a lot of controls, but the day-to-day work clusters into a handful of recognizable jobs:
- Create, suspend, and terminate cPanel accounts. The core function. Every new customer or site you host begins as a cPanel account created here.
- Set up hosting packages and plans. Packages bundle resource limits — disk space, bandwidth, email accounts, databases — into named tiers you assign to accounts. Think of them as the lease terms.
- Manage DNS. Configure DNS zones and nameservers at the server level so domains resolve correctly.
- Handle server security and the firewall. Apply server-wide protections, manage access rules, and keep the machine hardened against threats.
- Install and manage SSL. Issue and deploy SSL certificates across the accounts on the server so sites load securely over HTTPS.
- Monitor resources. Keep an eye on server load, disk usage, and account-level consumption so nothing runs away with the machine.
- Branding and private nameservers (for resellers). Skin the cPanel experience and run nameservers under your own domain so your hosting looks like *your* business, not someone else’s.
Each of these is a building-level lever. None of them belong to an individual website owner, which is precisely why they live in WHM rather than cPanel.
Why is WHM the engine behind reseller hosting?
This is the use case that makes WHM click for most people. Reseller hosting is, at its core, WHM access. When you buy a reseller plan, what you are really being handed is a WHM login with the authority to create and manage cPanel accounts.
The model is simple. You buy a block of hosting resources. Using WHM, you carve that block into hosting packages and create individual cPanel accounts — one for each of your customers. Each customer logs into *their* cPanel to run *their* website, completely unaware of the other accounts beside them. You, meanwhile, sit in WHM managing the whole operation: creating accounts when new customers sign up, suspending them if a bill goes unpaid, adjusting packages, and branding everything with your own logo and private nameservers so the service looks fully like your own company.
In landlord terms: reseller hosting hands you the keys to the building. WHM lets you create the apartments (cPanel accounts), set the lease terms (packages), keep the building secure, and put your own name on the front door. Your tenants never need to know there is a larger landlord upstream.
### Run or resell hosting with DarazHost
DarazHost reseller hosting gives you WHM — the landlord’s control panel — so you can create and manage cPanel accounts, set up hosting packages, and brand your own hosting business with private nameservers, all on fast SSD infrastructure. You get the admin power to run or resell hosting, with 24/7 support working quietly behind the scenes. It is the difference between renting an apartment and holding the keys to the whole building.
How do you access WHM?
You reach WHM through your browser, just like cPanel, but on a different port. The standard secure login port for WHM is 2087. You typically log in at an address that looks like `https://yourserver.com:2087`, using the administrator or reseller credentials provided by your host.
That port number is worth remembering because it is the quickest way to tell the two panels apart at login: 2087 takes you to WHM (the admin office), while 2083 takes you to cPanel (your apartment). Same building, two different doors.
If you are a reseller, your host will give you your WHM details when your plan is set up. From there, your first jobs are usually to define a hosting package and create your first cPanel account — and you are in business.
How do WHM and cPanel work together day to day?
A quick walk-through ties it all together. Imagine you have just started a small hosting business:
- You log into WHM on port 2087 using the reseller credentials from your host.
- You build a hosting package — say, “Starter” with a set amount of disk space, bandwidth, and email accounts.
- A customer signs up, so you create a new cPanel account for them in WHM and assign it the Starter package.
- The customer logs into their cPanel on port 2083, where they upload their website, set up email, and create a database — managing their unit and nothing else.
- You stay in WHM, monitoring server resources, keeping security tight, and creating more accounts as new customers arrive.
WHM and cPanel are doing two different jobs at two different levels, but they are halves of one whole. You manage the building; your customers manage their apartments. That is the entire relationship in a nutshell.
For a fuller tour of the end-user side of this system — the apartment, not the building — see the complete pillar guide: cPanel Explained: The Complete Beginner-Friendly Guide to Your Hosting Control Panel.
Frequently asked questions
Is WHM the same as cPanel? No. They are made by the same company and work together, but they operate at different levels. WHM (WebHost Manager) is the admin panel that manages the whole server and creates cPanel accounts. cPanel manages a single hosting account. WHM is the landlord’s panel; cPanel is the tenant’s.
Do I need WHM if I only have one website? Almost certainly not. If you are running a single site, everything you need lives in cPanel — email, files, databases, and SSL for your domain. WHM is for people who manage multiple accounts or an entire server, such as administrators and resellers.
Can I create cPanel accounts without WHM? No. Creating, suspending, and terminating cPanel accounts is an administrative, building-level action that happens inside WHM. That is precisely what WHM is for, and it is why reseller hosting is built on WHM access.
What port does WHM use? WHM is accessed on port 2087 for the secure login (for example, `https://yourserver.com:2087`). For comparison, cPanel uses port 2083. The different ports are a handy way to tell the two panels apart.
Is reseller hosting just WHM access? In essence, yes. A reseller plan gives you a WHM login with the authority to create and manage cPanel accounts, build hosting packages, and brand the service with your own private nameservers — letting you sell hosting under your own name.
