Hosting Terms
What is .htaccess?
.htaccess in plain English — the meaning, the comparison, and why it matters to anybody running a website.
Straight answer first
.htaccess is Apache's per-folder configuration file — a plain text control surface for redirects, rewrites, security rules and headers, with no access to the server config needed.
The sections below open it up properly — how it works, why a site owner should care, and a concrete example of it doing its job.
Written by the Hosting Seller staff · Checked 1 August 2026
0
Terms left unexplained
100+
Definitions, cross-linked
Real
Examples from real kit
Free
To read, naturally
WordPress permalinks are written into it, redirects stack up in it, and hardening rules — blocking access to files, forcing HTTPS, setting headers — are deployed through it. Changes apply the moment you save, with nothing to restart.
Its power is also its risk. One stray character takes the whole site to a 500 until you undo it, which is why copying the file before you edit it is the entire safety procedure.
.htaccess, by comparison
House rules pinned up at the entrance to each corridor. Staff read them before serving anybody beyond that point, and a garbled rule sheet stops service dead until somebody rewrites it legibly.
Keep that picture in mind and most of the documentation you will ever read on the subject stops being mysterious.
Why this one is worth knowing
It is the most accessible lever a site owner has over server behaviour. Nearly every redirect, security and caching recipe you will ever apply is an .htaccess recipe, applied in seconds and reversed just as fast.
That is the test for any technical term, incidentally — not 'do I understand it fully' but 'do I know when it is the answer to my problem'. For this one, you now do.
One concrete example
A migration's fifty page-to-page redirects live as fifty lines in .htaccess — versioned alongside the site, editable in File Manager, and live the instant the file is saved.
Multiply that example by every website on the internet and you have the concept's entire job description in one go.
The Hosting Seller angle
On our hosting this largely looks after itself — the platform applies sensible defaults, and the panel hands you the controls when you want them. The concepts worth reading next: Apache, 301 Redirect, HTTP Status Codes and Document Root.
Bring an existing site and we shift it across at no charge — usually inside 24 hours, with nothing going dark while we work.
Unexplained jargon is bad service
We treat unexplained jargon as a service failure. This glossary is the support desk's accumulated translations, published where a search engine can hand them out for us.
Real people answer the counter at any hour, including the awkward questions other hosts wave off as out of scope.
- 100+ terms, all in plain English
- Everyday comparisons and real examples
- Related concepts linked together
- Written by the people on the desk
Why Hosting Seller
On every plan, as standard
Grounded in real kit
Examples point at hosting you would actually use, not at an abstract diagram.
The stakes spelled out
Not only what it is, but when it turns out to be the answer to a problem you are having.
Linked, never siloed
Related terms cross-reference each other, so one lookup grows into a working understanding.
Honest about what to skip
Most terms are recognise-level rather than operate-level, and the glossary says which is which.
Plain English first
Every term defined for people who run sites, not for other sysadmins — jargon translated rather than restated.
One term, fully landed
.htaccess defined, pictured by comparison and placed in your own control panel — recognise-level in a single read.
First Steps
From choosing to live
- 1
Find it in your own account
The quickest way to learn a hosting term is to find it in your own panel; five minutes of looking beats an hour of reading about it.
- 2
Check what the defaults are
Confirm how your account has this set. It is usually right by default here, and now you will know rather than guess.
- 3
Follow the terms next door
Concepts travel in packs — Apache, 301 Redirect and HTTP Status Codes finish this one's picture, and each is a two-minute read away.
In the Box
Packed with every plan
- Mailboxes that carry your own domain name
- cPanel, the panel the rest of the trade already knows
- Site migration done for you by our staff, at no charge
- SSH, Git and Composer on the plans built for developers
- Spam and virus filtering fitted to every mailbox
- A free SSL certificate on every plan, reissued before it lapses
- Staging copies so changes get tested before they go live
- NVMe SSD storage on every shelf, not just the top one
- A 99.9% uptime commitment, watched by monitoring day and night
- PHP versions picked per site from the panel
Across the Counter
The questions we get asked most
I edited .htaccess and the entire site broke — why is it so fragile?
The server parses the file on every single request, so a malformed line becomes a 500 by design. Put your backup copy back, or delete the lines you added, and the site returns instantly. That same fragility is why edits take effect with zero delay.
Does .htaccess work on nginx as well?
No, and deliberately so — nginx ignores it and the equivalent rules go in the server configuration instead. On LiteSpeed, which is what we run, .htaccess works the Apache way, which is one reason the ecosystem's recipes apply here without translation.
Where do the servers actually sit?
Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.
Can I test changes somewhere safe first?
Yes — plans with staging let you clone the live site, work on the copy, then push it across when you are satisfied. It is the difference between hoping an update behaves and knowing that it does before any customer meets it.
What does round-the-clock support actually stretch to?
People at the counter at every hour, and a scope that takes in the practical work: mailbox setup, DNS records, WordPress trouble, restores. Not 'the server responds, ticket closed'. Ask us something hard before you order — the reply is a fair sample of what you would get afterwards.
Can I bring a domain I already own?
Yes, and transfers in are routine. Unlock the name at your present registrar, collect the auth code, then start the transfer from your client area. Whatever registration time is left comes across with it, and DNS keeps answering the whole way through.
Which control panel comes with the account?
cPanel, which the whole trade already knows. That means every tutorial online matches what you see, your backups restore onto any cPanel host anywhere, and what you learn here stays useful for life. Plesk and DirectAdmin are stocked on specific plans for anyone who prefers them.
Read next
Document Root
The document root is the folder a domain's web addresses map into — the boundary between your site's public…
Apache
Apache is the long-serving open-source web server whose conventions — .htaccess above all others — shaped t…
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and daily backups.
Domain Names
Search, register and transfer names — year one free with annual hosting.
Packing up and moving host? Take our checklist.
A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.
Do the launch properly this time.
From a first website to a rack of servers, moving up is a change to your account rather than a migration.
See the plans