phpinfo is a PHPPHP is a programming language that builds your web pages on the computer that hosts your site, just before they reach the visitor. WordPress runs on it. function that displays information about the environment in which it runs. A maintainer may use this information when investigating an update or a hostingWeb hosting is the service that keeps your website's files on a computer that is always online, so visitors can open your site at any time. move. As a website owner, you do not need to create a public diagnostic page to participate.
Start with the question you need answered and request only the information relevant to that question.
What information can appear?
The PHP reference for phpinfo describes output covering configuration, loaded modules and the PHP installation. Depending on the selected output, environment and request data can also appear. A complete report should therefore not be pasted into a public support forum without reviewing its contents first.
A PHP versionA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing., a list of PHP extensionsA PHP extension adds functions to PHP that a website or application may need. and configuration values answer different questions. Ask for an explanation of the relevant part. A large technical report is not automatically a diagnosis.
You need to know which observation helps explain the problem and which finding still needs further investigation.
Begin with a focused question
Which PHP version does your site report?
We read only what your site already sends in public: the headers and the top of the homepage. No scan, no login.
Suppose a website stops processing images after moving hosts. Ask which details are needed to compare the previous and replacement environments. Have the developer identify the relevant extension or setting.
Avoid sending a complete copy of server information to everyone involved simply because it might contain something useful.
Include the exact failed action in the request. Name the domainA domain name is the address people type to reach your website, such as yourcompany.com. It points visitors to wherever your site is hosted., when the problem started and what you expected to happen. Ask whether the diagnostic check was performed in the environment serving that website.
A report from a terminal or another test site should be clearly identified rather than silently treated as production evidence.
Keep the observation separate from the conclusion. A value appearing in the output is one fact; deciding whether it explains the failure is another step. Ask the maintainer to support that connection.
An incidental difference between two environments should not become the accepted cause simply because it is easy to point at.
How should configuration values be interpreted?
The output can show local and master values for settings. Ask which value applies to the request under investigation. The explanation of php.iniphp.ini is the settings file for PHP on your hosting. It sets limits, such as how much memory a script may use, how big an upload may be and if errors show. provides background on PHP configuration, but the name of a configuration file alone does not explain why a particular value is active for this website.
When a change is needed, record the original value, the replacement and where they were observed. Agree which problem the adjustment should resolve. Repeat the relevant website action afterwards.
A correct configuration value can form part of the evidence, but it does not replace checking the function your visitors actually use.
If two reports disagree, collect their context before making further adjustments. Were they produced on the same date, for the same domain and in the same environment? Ask the maintainer to explain the discrepancy.
Changing several settings at once makes it harder to understand later which change affected the outcome.
How should you share the result?
Prefer a summary of the relevant fields. Have a maintainer review what can be shared with an external supplier. Keep cookies, credentials and complete request contents out of support messages.
The verified version, the relevant component and a description of the discrepancy are often enough to frame the initial technical question.
For temporary diagnostics, agree who receives access and when that access ends. Ask the maintainer to confirm that temporary facilities are removed or restricted again after use. This is part of arranging the investigation responsibly, even when you only receive the final result and never access the diagnostic screen yourself.
Keep a short conclusion in your maintenance notes with the date, environment and next action. Someone reading it later should be able to understand why the adjustment was made. A raw report without explanation is less helpful for that purpose than a concise account tied directly to the original question.
What does phpinfo not establish?
An environment report does not demonstrate that every website function works. After a PHP update, repeat the important visitor journey, such as completing a form and checking that it was received. Record what was not tested as well.
This prevents a small technical check being mistaken for acceptance of the whole website.
The hosting guides help you locate the appropriate administration environment. Use the Error Hub for recognisable errors and the status page for maintenance context. If you plan to update PHP in WordPress, provide a reviewed summary.
Ask for help with the specific question about your environment that remains unresolved.
Frequently asked questions
Do I need a public phpinfo page?
No. Ask your maintainer for a restricted check and a summary of relevant findings.
Can I share a complete report?
Have its contents reviewed first. The output can include information unsuitable for a public support request.
Does phpinfo prove my site works?
No. It describes the examined environment. Check important website functions separately after a change.