display image using php

display image using php

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Debugging Image Display Issues in PHP and SQL

You are encountering a classic case of "wrong path, wrong format." The symptom—a tiny thumbnail appearing instead of the full image—usually indicates that the browser is receiving an HTTP 403 Forbidden or 404 Not Found error. When this happens, modern browsers often render a small default icon rather than showing an explicit error message.

Looking at your code, there are three distinct issues preventing the image from loading correctly. First, you are using the deprecated mysql_* functions, which were removed in PHP 7.0. Second, and more critically, you are not checking whether the database query actually returned a row before attempting to access it. Third, your src attribute is likely malformed because you are not properly escaping the variable or ensuring it contains an absolute URL.

The Empty Row Problem

The most immediate logic flaw is in how you handle the $profileimage result set. You execute a query and immediately call mysql_fetch_array(). If the user does not have an image, or if there is a SQL syntax error, this function returns false. When you try to access $row['imagefile'] on a false value, PHP issues a warning and assigns an empty string (or null) to $showimage.

Your HTML then renders as:

<img src = "">

Browsers treat an empty src by displaying a broken image icon or a tiny placeholder. You must explicitly check if the row exists before using it:

$row = mysql_fetch_array($profileimage);

if ($row) {
    $showimage = $row['imagefile'];
} else {
    // Handle the case where no image exists
    $showimage = '/images/placeholder.png'; 
}

Relative vs. Absolute Paths

Assuming $showimage contains a valid filename (e.g., uploads/john_avatar.jpg), simply placing that string inside <img src="..."> expects the file to be in the web root or a relative folder structure that matches your server's configuration. If your database stores only the filename without the directory path, and that file isn't physically located at the root of your domain, the browser cannot find it.

If your application is served from /var/www/html/ and your images are stored in /var/www/html/uploads/, but the database column contains only john.jpg, you need to prepend the directory:

$showimage = 'uploads/' . $row['imagefile'];

Furthermore, if you expect the image to load from a different domain or a CDN, $showimage must be an absolute URL (e.g., https://example.com/uploads/john.jpg). Hardcoding the protocol and domain into your PHP string ensures cross-origin compatibility.

Security Considerations with mysql_*

Your query concatenates the username directly into the SQL string:

SELECT * FROM images WHERE username='$username'

While this works for testing, it is vulnerable to SQL injection if $username contains malicious input from the session. Additionally, mysql_* functions are deprecated and removed in modern PHP versions. You should migrate to mysqli or PDO immediately. With mysqli, you can use prepared statements to sanitize inputs automatically:

$stmt = $mysqli->prepare("SELECT imagefile FROM images WHERE username = ?");
$stmt->bind_param('s', $username);
$stmt->execute();
$stmt->bind_result($showimage);
$stmt->fetch();

This approach prevents injection attacks and handles the data types safely.

Final Implementation Checklist

Before expecting the full image to render, verify these three conditions:

  1. Existence: Ensure $row is not false and that imagefile contains a value.
  2. Path Validity: Confirm that the file path in the database corresponds exactly to where the file sits on the server (including subdirectories).
  3. Permissions: Ensure the web server user (often www-data) has read permissions for the directory containing the image files.

If you are building a larger application, consider leveraging Laravel's asset management or storage APIs, which handle path resolution and security much more robustly than raw PHP strings. For further guidance on modernizing legacy PHP applications with secure practices, visit https://laravelcompany.com.

Our network