A file named makers.php3 splits into two halves, and each half answers a different question. The word "makers" was chosen by whoever built the page. The .php3 extension is the informative part: it marks a web script written for PHP 3, the generation of the language that the PHP manual's history page dates to June 1998.[1] The file itself is plain text, and under the defaults PHP documents today, a server will not execute it. Those two facts answer most of the question: what the file is, what opens it, and where the name comes from.
The .php3 extension marks PHP 3-era server-side script
FileInfo's dictionary entry describes a .php3 file as a web page that may contain PHP 3 code.[2] The mechanics matter more than the label. The entry states that the PHP code within the page is parsed by a PHP engine on the web server, which dynamically generates HTML that is sent to the user's web browser, often in combination with a database such as MySQL.[2] The logic never reaches the visitor. The visitor receives the HTML the server produced, and the code that produced it stays on the server.
That division of labor is also where the modern gap sits. The same entry notes that PHP pages generally use the .php extension today, and its last update is dated December 21, 2018, which puts the .php3 write-up several generations behind the language.[2] Solvusoft's entry, amended August 5, 2026, still describes the extension as a single known file type, the "PHP 3 Web Page" format, and rates its popularity "Low" among files found on typical desktop and mobile devices.[3] Both sites are commercial dictionaries, and on the identity of the format they agree: a web page containing PHP 3 code.
A text editor opens it; a browser only shows the code
The file is text, and any text editor displays it. FileInfo lists a text editor or web development program as the way to edit PHP3 pages, and its program list runs from PHP itself and Apache Web Server with the PHP engine to Eclipse PDT, Adobe Dreamweaver 2021, EditPlus, gVim, TextMate, and Vim.[2] Solvusoft's list overlaps on six of its eight entries.[3] Every list includes free editors, and viewing the file costs nothing. Solvusoft's page carries repeated offers for its own paid FileViewPro product, yet a basic editor shows every byte the file contains.[3]
A browser behaves differently. The PHP code was written to run on the server, so a browser opening the file directly has no engine to interpret it and shows the source text as-is. Whatever the page once did for visitors, it did it after a server-side PHP engine processed the code.[2] The finished page never existed inside the file. Only the instructions for building it did.
The name dates to PHP 3, announced in June 1998
The manual's history section records that PHP 3.0 was announced in June 1998 by the new PHP Development Team as the official successor to PHP/FI 2.0. The rewrite behind it began in 1997, when Andi Gutmans and Zeev Suraski found PHP/FI 2.0 inefficient for an eCommerce application they were developing for a university project. PHP 3.0 was the first version that closely resembles PHP as it exists today, and the language settled into its recursive name, PHP: Hypertext Preprocessor, in the same period.[1]
The language's early adoption numbers give the extension its reach. The history page records the announcement landing when PHP 3.0 was already installed on over 70,000 domains around the world. A Netcraft survey from May 1998 counted nearly 60,000 domains reporting PHP headers, about 1 percent of domains on the internet at the time. At its peak, PHP 3.0 was installed on approximately 10 percent of the web servers on the internet.[1] Scripts written for that generation carried the .php3 extension.
The era ended with a version change. PHP 4.0, built on the Zend Engine first introduced in mid 1999, was officially released in May 2000, and new PHP pages moved to .php.[1] The old label survives in php.net's own archive: the PHP Museum's release index keeps a php3/ directory alongside php1, php2, php4, php5, php7, and php8, and the history page still points readers there to "touch a piece of Internet history."[4]
PHP's documented defaults do not execute .php3
PHP's installation guide for Apache shows how a modern server decides what to execute.[5] The default example in the manual maps only files ending in .php to the PHP handler, and the manual explains the choice as a safety measure: the restrictive pattern keeps uploaded files such as exploit.php.jpg from being executed as PHP. Extending execution to .php3 requires an administrator to add it explicitly. The manual demonstrates this as an optional variant, a pattern that extends the handler to .php2, .php3, .php4, .php5, .php6, and .phtml files.[5]
The same guide warns against using mod_php for new installations at all, recommending PHP-FPM with Apache's mod_proxy_fcgi module instead, the setup major Linux distributions ship as their default configuration.[5] PHP's built-in development server shows the same default at the entry-point level: when a request names no file, it looks for index.php or index.html, and index.php3 is not part of that lookup.[6]
These statements describe the configurations PHP documents itself. How a given hosting provider maps extensions is that provider's configuration decision, and this article does not survey hosts. What the documentation establishes is a clear default: under the setups PHP publishes, a .php3 file is not executed. Where a .php3 page still works, the mapping to the PHP engine was added by hand.
Three steps to check a makers.php3 file
For anyone holding the file itself, three steps cover it.
- Open it in a text editor. The contents read as HTML with embedded PHP code, and that is the entire file. Nothing needs to be installed to view it.
- Leave it untrusted until the origin is clear. The extension dates the page's target generation. It says nothing about who wrote the code or what the code does, so a script from an unknown source stays text until its source is established.
- Do not expect the browser view to resemble the page. The HTML visitors once saw existed only after a PHP engine processed the code on a server, and the file alone cannot reproduce that.
The file name carries most of the answer. makers.php3 is a page called makers, written for the generation of PHP that ran from June 1998 to May 2000, reached approximately 10 percent of the web's servers at its peak, and handed over to PHP 4 with the .php extension taking its place. As a file it is text: any editor shows it, a browser alone displays the code, and a server configured the way PHP documents today leaves it untouched. Where such a page still executes, it runs because an administrator deliberately mapped the old extension, and only because of that configuration.