WP 6.8.2 - In the Media Library some images have an empty preview in both views.

[garrigan]

Note: This issue did not occur in the previous version.

The image is visible within "Attachment details".

The "developer tools" indicates the file size is very small. Example: 391 B, 428 B

Test environment: New installation without any changes.

I did empty the browser cache.

I have repeated the process a few times.

I can provide the images.

It should be noted that I am not an expert with WordPress. I am an unemployed IT guy who had supported on-premises Windows-based servers. The site is for my job search.

Feel free to ask for additional information.

[garrigan]

First affected file

[garrigan]

Second affected file

[Presskopp]

Hi and welcome, James,

I am unable to reproduce the issue you describe. Can you please provide more details about your environment and maybe screenshots. Thank you.

[garrigan]

Site Health Info - Dev1 site

[garrigan]

I uploaded both images and a text file with the site info.

[Presskopp]

just for reference, working for me

[garrigan]

I saw your attached image. Perhaps the uploaded image files are changed by this ticket system. Does a method exist to upload the files as a zip file? I can provide access to the test environment. It is a VMware workstation snapshot.

[garrigan]

Note: Within 9-previous-wordpress-version-all-images-are-visible.png image number 30 "cement texture" is nearly the same color as the background.

[garrigan]

image 10-contents-of-wp-content-uploads-2025-07.png

The files that are 1 KB in size are blank or empty images. When I open the 1 KB files with an image viewer I do not see anything.

[audrasjb]

Hello and welcome to WordPress Core Trac,

Moving to milestone 6.8.3, pending detailed review.

[garrigan]

11-contents-1kb-files-from-wp-content-uploads-2025-07.png
I opened each 1 KB image file with a text editor.

[garrigan]

I realized it has been a while since I last imported images from an initial installation of WordPress.

It fails with 6.8 and I am successful with 6.6.

On Friday I will try each version with a fresh installation.

I will report the last successful version for which all the image files are visible.

[garrigan]

The issue does not appear within the following versions of WordPress.
6.7 good
6.7.1 good
6.7.2 good

Based on my testing, I initially see the issue within WordPress version 6.8

[garrigan]

My test environment is consistent.

I revert to the same snapshot, and I execute the same bash scripts. I only change --version=

[monikarao]

I tested this multiple times but couldn’t reproduce the issue.
OS: Mac
Browsers: Chrome and Safari

Screenshot: ​https://prnt.sc/SoXqa8v2ibcN

[garrigan]

Hi,
I was also importing the images via the WordPress importer. I can create an externally accessible test environment.

[garrigan]

It has been nearly two weeks since the last update to this ticket and thus I am following up on this issue.

Based on my initial information, the internet browser is not the proximate cause of the issue.

My test environment is consistent. I revert to the same snapshot, and I execute the same bash scripts. I only change --version=

The issue does not appear within the following versions of WordPress.
6.7 good
6.7.1 good
6.7.2 good

Based on my testing, I initially see the issue within WordPress version 6.8

I provided images to illustrate the issue.

To be fair to Monica, our test environments are different. Monica: (OS: Mac) -- Me: (Rocky Linux 9.5)

I can create an externally accessible test environment without third-party plugins.

Another option could be to use some type of software to allow remote viewing of my test environment while I execute the steps to illustrate the issue.

Both options would require scheduling ...

Additional details from the current test environment are shown below. The PRODUCTION environment has different specifications.

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1810
imagemagick_version: ImageMagick 7.1.2-1 Q16-HDRI x86_64 23308 ​https://imagemagick.org
imagick_version: 3.8.0
file_uploads: 1
post_max_size: 512M
upload_max_filesize: 512M
max_effective_size: 512 MB
max_file_uploads: 20
imagick_limits:

imagick::RESOURCETYPE_AREA: 30 GB
imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
imagick::RESOURCETYPE_FILE: 768
imagick::RESOURCETYPE_MAP: 15 GB
imagick::RESOURCETYPE_MEMORY: 7 GB
imagick::RESOURCETYPE_THREAD: 1
imagick::RESOURCETYPE_TIME: 9.2233720368548E+18

imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, ASHLAR, AVCI, AVI, AVIF, AVS, BAYER, BAYERA, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUBE, CUR, CUT, DATA, DCM, DCR, DCRAW, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FARBFELD, FAX, FF, FFF, FILE, FITS, FL32, FLV, FRACTAL, FTP, FTS, FTXT, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, HALD, HDR, HEIC, HEIF, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICN, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, JXL, K25, KDC, KERNEL, LABEL, M2V, M4V, MAC, MAP, MASK, MAT, MATTE, MDC, MEF, MIFF, MKV, MNG, MONO, MOS, MOV, MP4, MPC, MPEG, MPG, MPO, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORA, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PHM, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PS, PS2, PS3, PSB, PSD, PTIF, PWP, QOI, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGB565, RGBA, RGBO, RGF, RLA, RLE, RMF, RSVG, RW2, RWL, SCR, SCT, SF3, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, SRW, STEGANO, STI, STRIMG, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TM2, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YAML, YCBCR, YCBCRA, YUV
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM
ghostscript_version: 9.54.0

### wp-server ###

server_architecture: Linux 5.14.0-570.33.2.el9_6.x86_64 x86_64
httpd_software: nginx/1.29.1
php_version: 8.3.24 64bit
php_sapi: fpm-fcgi
max_input_variables: 5000
time_limit: 30
memory_limit: 512M
max_input_time: -1
upload_max_filesize: 512M
php_post_max_size: 512M
curl_version: 7.76.1 OpenSSL/3.2.2
suhosin: false
imagick_availability: true
pretty_permalinks: true
static_robotstxt_file: false
current: 2025-08-28T15:48:14+00:00
utc-time: Thursday, 28-Aug-25 15:48:14 UTC
server-time: 2025-08-28T11:48:13-04:00

### wp-database ###

extension: mysqli
server_version: 10.6.23-MariaDB
client_version: mysqlnd 8.3.24
max_allowed_packet: 16777216
max_connections: 151

[jorbin]

6.8.3 was a security only release. Punting though 6.8.4 is not planned as a release

[riccardodicurti]

I tested this issue using the official Docker environment and downgraded to version 6.8 with:

wp core update --version=6.8 --force

I wasn’t able to reproduce the issue.

@garrigan, could you please confirm whether you’re also working within a Docker environment?

Ciao from WordCamp Verona

`
### wp-core ###

version: 6.8
site_language: en_US
user_language: en_US
timezone: +00:00
permalink: /%year%/%monthnum%/%day%/%postname%/
https_status: false
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: local
user_count: 1
dotorg_communication: true

### wp-paths-sizes ###

wordpress_path: /var/www/src
wordpress_size: 102.76 MB (107747004 bytes)
uploads_path: /var/www/src/wp-content/uploads
uploads_size: 7.04 MB (7378343 bytes)
themes_path: /var/www/src/wp-content/themes
themes_size: 44.90 MB (47079974 bytes)
plugins_path: /var/www/src/wp-content/plugins
plugins_size: 332.45 KB (340424 bytes)
fonts_path: /var/www/src/wp-content/uploads/fonts
fonts_size: directory not found
database_size: 2.14 MB (2244608 bytes)
total_size: 157.16 MB (164790353 bytes)

### wp-active-theme ###

name: Twenty Twenty-Three (twentytwentythree)
version: 1.6
author: the WordPress team
author_website: ​https://wordpress.org
parent_theme: none
theme_features: core-block-patterns, post-thumbnails, responsive-embeds, editor-styles, html5, automatic-feed-links, widgets-block-editor, block-templates
theme_path: /var/www/src/wp-content/themes/twentytwentythree
auto_update: Disabled

### wp-themes-inactive (14) ###

Twenty Eleven: version: 4.9, author: the WordPress team, Auto-updates disabled
Twenty Fifteen: version: 4.0, author: the WordPress team, Auto-updates disabled
Twenty Fourteen: version: 4.3, author: the WordPress team, Auto-updates disabled
Twenty Nineteen: version: 3.1, author: the WordPress team, Auto-updates disabled
Twenty Seventeen: version: 3.9, author: the WordPress team, Auto-updates disabled
Twenty Sixteen: version: 3.6, author: the WordPress team, Auto-updates disabled
Twenty Ten: version: 4.4, author: the WordPress team, Auto-updates disabled
Twenty Thirteen: version: 4.4, author: the WordPress team, Auto-updates disabled
Twenty Twelve: version: 4.6, author: the WordPress team, Auto-updates disabled
Twenty Twenty: version: 2.9, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Five: version: 1.2, author: the WordPress team (latest version: 1.3), Auto-updates disabled
Twenty Twenty-Four: version: 1.3, author: the WordPress team, Auto-updates disabled
Twenty Twenty-One: version: 2.6, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Two: version: 2.0, author: the WordPress team, Auto-updates disabled

### wp-plugins-inactive (2) ###

Akismet Anti-spam: Spam Protection: version: 5.3.7, author: Automattic - Anti-spam Team (latest version: 5.5), Auto-updates disabled
Hello Dolly: version: 1.7.2, author: Matt Mullenweg, Auto-updates disabled

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1691
imagemagick_version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 ​https://imagemagick.org
imagick_version: 3.7.0
file_uploads: 1
post_max_size: 1G
upload_max_filesize: 1G
max_effective_size: 1 GB
max_file_uploads: 20
imagick_limits:

imagick::RESOURCETYPE_AREA: 122 MB
imagick::RESOURCETYPE_DISK: 1073741824
imagick::RESOURCETYPE_FILE: 786432
imagick::RESOURCETYPE_MAP: 512 MB
imagick::RESOURCETYPE_MEMORY: 256 MB
imagick::RESOURCETYPE_THREAD: 1
imagick::RESOURCETYPE_TIME: 9.2233720368548E+18

imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI, AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
gd_version: bundled (2.1.0 compatible)
gd_formats: GIF, JPEG, PNG, WebP, BMP
ghostscript_version: 9.53.3

### wp-server ###

server_architecture: Linux 6.10.11-linuxkit x86_64
httpd_software: nginx/1.27.2
php_version: 8.2.25 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 30
memory_limit: 128M
admin_memory_limit: 256M
max_input_time: -1
upload_max_filesize: 1G
php_post_max_size: 1G
curl_version: 7.74.0 OpenSSL/1.1.1w
suhosin: false
imagick_availability: true
pretty_permalinks: true
static_robotstxt_file: false
current: 2025-10-10T08:40:37+00:00
utc-time: Friday, 10-Oct-25 08:40:37 UTC
server-time: 2025-10-10T08:40:36+00:00

### wp-database ###

extension: mysqli
server_version: 8.0.40
client_version: mysqlnd 8.2.25
max_allowed_packet: 67108864
max_connections: 151

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /var/www/src/wp-content
WP_PLUGIN_DIR: /var/www/src/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: true
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: true
SCRIPT_DEBUG: true
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: local
WP_DEVELOPMENT_MODE: core
DB_CHARSET: utf8
DB_COLLATE: undefined

### wp-filesystem ###

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
fonts: does not exist

`

[garrigan]

Hi, I am not working within a Docker environment.

I attached the file Site Health Info.txt when I created the ticket. It is the third attachment.

Link to the Site Health Info.txt file:
https://core.trac.wordpress.org/attachment/ticket/63708/Site%20Health%20Info%20.txt

[garrigan]

Feel free to reach out to me with additional questions or concerns.

[garrigan]

I repeated the same test with the current version of WordPress 6.8.3. The issue exists in the current version of WordPress 6.8.3.

[desrosj]

There are currently no plans to ship a 6.8.4 release with 6.9 RC1 having been published earlier this week.

@garrigan My apologies that this one has not received the attention it needs. I'm punting this to 6.9.1 so it can be considered during the next minor release cycle.

[garrigan]

Hi Jonathan,

When the person/team is ready to examine the issue I found, would it be possible for me to collaborate with the person/team to help the person/team replicate my environment?

In my opinion it will be important to do so, because the previous two folks used different environments and consequently, both people were not able to replicate the problem.

As stated in the notes, I am using NGINX on top of Rocky Linux 9.5 for my test environment.

The issue occurs with the most basic NGINX configuration.

I check email during Eastern time zone hours.

Thank you,

Jim Garrigan

Replying to desrosj:

There are currently no plans to ship a 6.8.4 release with 6.9 RC1 having been published earlier this week.

@garrigan My apologies that this one has not received the attention it needs. I'm punting this to 6.9.1 so it can be considered during the next minor release cycle.

[wildworks]

As far as I can see, no one has been able to reproduce the issue yet, and it's unclear whether the issue is with WordPress itself. I'd be grateful if anyone else could test this issue.

[garrigan]

The previous two folks used different environments and consequently, both people were not able to replicate the problem.

As stated in the notes, I am using NGINX on top of Rocky Linux 9.5 for my test environment.

The issue occurs with the most basic NGINX configuration.

Replying to wildworks:

As far as I can see, no one has been able to reproduce the issue yet, and it's unclear whether the issue is with WordPress itself. I'd be grateful if anyone else could test this issue.

[wildworks]

I installed Rocky Linux on a virtual machine and tried to set up a WordPress environment, but I was unable to complete the setup.

[garrigan]

I can provide a test environment.

Replying to wildworks:

I installed Rocky Linux on a virtual machine and tried to set up a WordPress environment, but I was unable to complete the setup.

[SirLouen]

Replying to wildworks:

I installed Rocky Linux on a virtual machine and tried to set up a WordPress environment, but I was unable to complete the setup.

If you run the WP env inside Rocky Linux, you defeat the whole purpose of the test.

I can provide a test environment.

Ideally to test this I would take any of the wpenv-docker-image and switch Debian for Rocky Linux (and changing a bit the dependencies). @garrigan if you could provide a Dockerfile with an nginx and and WP running over it, would be clutch.

[garrigan]

Hi,

I do not have any experience with Docker.

Why is the goal to not replicate the environment that exhibits the reported issue?

I don't understand "would be clutch".

Jim

Replying to SirLouen:

Replying to wildworks:

I installed Rocky Linux on a virtual machine and tried to set up a WordPress environment, but I was unable to complete the setup.

If you run the WP env inside Rocky Linux, you defeat the whole purpose of the test.

I can provide a test environment.

Ideally to test this I would take any of the wpenv-docker-image and switch Debian for Rocky Linux (and changing a bit the dependencies). @garrigan if you could provide a Dockerfile with an nginx and and WP running over it, would be clutch.

[garrigan]

I have a suggestion.

Within a few days, I can create and publish a YouTube video to visually show the issue.

[garrigan]

I revisited this issue with a simple NGINX configuration and the same images.

I am using the same Rocky Linux 9.5 virtual machine albeit with all the current updates.

The issue still exists in WordPress version 6.8.2.

The issue does not exist in WordPress version 6.9.

The results suggest something in the version 6.8.x series is causing the issue.

The results suggest something in version 6.9 resolves the issue.

My recommendation is for someone to carefully review a detailed list of changes from 6.7.x through 6.9.

I check email at least once per day. Time Zone: (GMT - 5)

[desrosj]

Replying to garrigan:

The issue does not exist in WordPress version 6.9.

Ah, this is great to hear!

Replying to garrigan:

I have a suggestion.

Within a few days, I can create and publish a YouTube video to visually show the issue.

Just for future knowledge, a video may help others visually see what is going on, the primary blocker here was that another contributor has been unable to reproduce the problem.

Until that happens and the steps/conditions/requirements are clarified, it's near impossible to figure out exactly what the cause of a problem is or what a reasonable fix may be.

I looked back for some possible changes that may have resolved this. I'm not sure if any of these are responsible, but they make improvements to the logic around processing PNG images so are possibly related:

• Improve Imagick handling of indexed PNG images with transparency [60667]
• Fix degraded handling for 24 bit PNG uploads [60246]

Since this issue seems to have resolved itself in 6.9, I am going to close this out as worksforme. If you experience the issue same issue in the future, feel free to reopen this and add more details.

Good luck in your job search, and thank you for taking the time to not only file this bug report, but to also follow up on it periodically!

[garrigan]

Hi Jonathan,

Not directed to you.
With regard to reproducing the problem, it is important to replicate the environment in which the problem exists.

After the problem is confirmed within a replica of the affected environment, the next step could be to repeat the scenario in the prototype/pristine/master/ideal/perfect environment.

Especially with open-source software, there are numerous components that can introduce a problem.

I have been involved with IT for too many years.
Sometimes, the one in a million chance edge cases do occur. Sometimes the coin does land on its edge.

I agree with the following:
Just for future knowledge, a video may help others visually see what is going on, the primary blocker here was that another contributor has been unable to reproduce the problem.

Until that happens and the steps/conditions/requirements are clarified, it's near impossible to figure out exactly what the cause of a problem is or what a reasonable fix may be.

Many thanks to you for "Good luck in your job search"

You are welcome -- "thank you for taking the time to not only file this bug report, but to also follow up on it periodically!"

I try to Do the Right Thing -- Spike Lee.

In the present time, online job applications cannot comprehend the concept and unfortunately many of the humans do not respect diligence/good practices. You and perhaps a few others are good exceptions.

Replying to desrosj:

Replying to garrigan:

The issue does not exist in WordPress version 6.9.

Ah, this is great to hear!

Replying to garrigan:

I have a suggestion.

Within a few days, I can create and publish a YouTube video to visually show the issue.

Just for future knowledge, a video may help others visually see what is going on, the primary blocker here was that another contributor has been unable to reproduce the problem.

Until that happens and the steps/conditions/requirements are clarified, it's near impossible to figure out exactly what the cause of a problem is or what a reasonable fix may be.

I looked back for some possible changes that may have resolved this. I'm not sure if any of these are responsible, but they make improvements to the logic around processing PNG images so are possibly related:

• Improve Imagick handling of indexed PNG images with transparency [60667]
• Fix degraded handling for 24 bit PNG uploads [60246]

Since this issue seems to have resolved itself in 6.9, I am going to close this out as worksforme. If you experience the issue same issue in the future, feel free to reopen this and add more details.

Good luck in your job search, and thank you for taking the time to not only file this bug report, but to also follow up on it periodically!