PHP stands for PHP: Hypertext Preprocessor. Yes, the acronym contains itself — that is deliberate, and it is called a recursive acronym. It originally stood for Personal Home Page, which is what Rasmus Lerdorf called the set of CGI scripts he wrote in 1994 to track visits to his online resume.
It is a strange answer to a simple question, and the strangeness is the interesting part. The rename tells you something real about how PHP grew: it was never designed as a language, it accumulated into one, and by the time anyone thought about branding it was already too widely deployed to rename properly.
Table of contents
- From Personal Home Page to a recursive joke
- Why the name is still slightly wrong
- The honest state of PHP in 2026
- Where PHP actually runs
- Running PHP without becoming a sysadmin
- How this fits the rest of the stack
- FAQ
From Personal Home Page to a recursive joke
In 1994 Rasmus Lerdorf wrote a handful of C binaries to log traffic to his personal site. He called the collection Personal Home Page Tools. It was not a language; it was a CGI toolkit with a template syntax bolted on.
In 1995 he released it publicly as PHP/FI — Personal Home Page / Forms Interpreter — which added form handling and rudimentary database access. Still not really a language, but people were using it as one.
In 1997 Andi Gutmans and Zeev Suraski rewrote the parser wholesale for what became PHP 3. That rewrite is where PHP stops being a toolkit and starts being a language, and it is where the name changed to the recursive form.
The recursion was a nod to GNU, which stands for GNU’s Not Unix, a convention already established in hacker culture. The Free Software Foundation had made self-referential naming a small tradition; PHP joined it.
The engine from that rewrite became the Zend Engine, from Zeev and Andi, which still powers PHP today.
Why the name is still slightly wrong
Hypertext Preprocessor describes what PHP did in 1997: you wrote an HTML file, sprinkled in <?php ?> blocks, and the interpreter preprocessed them before the server sent the result. The output was hypertext. The language preprocessed it. Accurate.
That is not what most PHP does now. A modern PHP application is a framework routing requests to controllers, talking to a database through an ORM, returning JSON to a client that renders it. There is often no HTML anywhere in the pipeline.
The name survives because renaming a language with this much deployed code is not a technical decision, it is an economic one. Every book, tutorial, file extension, MIME type, and job listing carries the name. The cost is enormous and the benefit is aesthetic.
The honest state of PHP in 2026
PHP has a reputation problem earned largely by PHP 4 and 5, and largely fixed by PHP 7 and 8. Anyone whose opinion formed before 2015 is describing a language that no longer exists.
- PHP 7 roughly doubled throughput over 5.6 and halved memory use, via a rewritten value representation in the engine. This was not incremental.
- PHP 8 added a JIT compiler, named arguments, union types, constructor property promotion,
matchexpressions, nullsafe operators, and attributes. - The type system is now genuinely useful. Scalar type declarations, return types, and
declare(strict_types=1)give you a checkable contract. Static analysers go considerably further. - Composer solved dependency management properly, and PSR standards made libraries interoperable in a way the PHP 4 ecosystem never managed.
The remaining criticism that lands is the standard library: inconsistent function names, inconsistent argument order, inconsistent return conventions. strpos returns false on failure and 0 on a match at position zero, which has generated bugs for thirty years. That is a real wart and it is not going away, because fixing it breaks everything.
Where PHP actually runs
The often-quoted figure is that PHP powers somewhere in the region of three quarters of websites whose server-side language can be identified. Treat the precise number with suspicion — the methodology behind those surveys is weak — but the order of magnitude is not in doubt.
The reason is WordPress, which is PHP, and which runs a large fraction of the web on its own. Add Drupal, Joomla, Magento, Laravel, and Symfony and you have covered an enormous amount of deployed software.
This is the practical argument for knowing what PHP is even if you never write it. If you maintain websites, you will at some point open a functions.php, read a stack trace from a plugin, or need to know why a page is slow. That is PHP whether or not it is your language.
It is also why PHP version choice is an operational decision rather than a preference. Each PHP release gets two years of active support and one further year of security fixes. Running a site on a version past that window means unpatched vulnerabilities in the layer that touches every request.
Running PHP without becoming a sysadmin
The classic PHP deployment story is a shared host, an FTP client, and a wp-config.php you edit in place. It works, and it is also how sites end up on PHP 7.4 in 2026 with nobody quite sure how to move.
The modern version separates the runtime from the code. The application is a repository, the PHP version is configuration, and an upgrade is a redeploy you can roll back rather than a migration you perform on a live server.
Managed WordPress on RunxBuild takes that shape, with a file manager and a database browser in the dashboard so the two things you actually need shell access for are available without it. Plans start at $3/month for the Starter tier. The WordPress file documentation covers what the file manager reaches.
For non-WordPress PHP — a Laravel or Symfony application — the Docker path is the general answer: define the runtime in the image, push the repository, get a build log and a live route.
How this fits the rest of the stack
PHP stands for PHP: Hypertext Preprocessor, which is a joke about GNU that outlived its own accuracy. The more useful fact is that the language people dismiss from memory was substantially rebuilt twice, and it still sits underneath a very large share of the working web. If you are sizing a WordPress or Laravel deployment and want the runtime, database, and bandwidth as separate line items, the RunxBuild hosting calculator shows them individually.
Useful related references:
- The Uploaded File Exceeds the upload_max_filesize Directive: Fixing It in the Right Place
- Services on RunxBuild
FAQ
What does PHP stand for?
PHP: Hypertext Preprocessor. It is a recursive acronym, meaning the first letter stands for the acronym itself. It originally stood for Personal Home Page when Rasmus Lerdorf released it in 1994.
Why did PHP change its name?
The 1997 rewrite by Andi Gutmans and Zeev Suraski turned a personal CGI toolkit into a general-purpose language. Personal Home Page no longer described what it was, and the recursive form followed the convention set by GNU, which stands for GNU’s Not Unix.
Is PHP still used in 2026?
Extensively. WordPress alone accounts for a large fraction of the web and is written in PHP, alongside Drupal, Magento, Laravel, and Symfony. PHP 8 with its JIT compiler is a substantially different language from the PHP 5 that shaped its reputation.
What is a recursive acronym?
An acronym whose expansion contains the acronym itself. PHP: Hypertext Preprocessor is one; GNU’s Not Unix is the best-known example, and it is where PHP borrowed the convention.
What PHP version should I be running?
The most recent version your application supports. PHP releases get roughly two years of active support plus one more year of security fixes, so anything past that window is running unpatched in the layer that handles every request.