{"id":114,"date":"2021-02-19T07:46:10","date_gmt":"2021-02-19T07:46:10","guid":{"rendered":"http:\/\/simongarrett.uk\/simon\/?page_id=114"},"modified":"2025-05-06T17:28:52","modified_gmt":"2025-05-06T16:28:52","slug":"test-profile-treatment","status":"publish","type":"page","link":"https:\/\/simongarrett.uk\/simon\/colour-management-information\/test-profile-treatment\/","title":{"rendered":"Test profile treatment"},"content":{"rendered":"\n

Test page to experiment with WordPress maltreatment of colour information.<\/em><\/p>\n\n\n\n

Updated 6th may 2025<\/p>\n\n\n\n

This page should render the colour blobs below the same as on the Colour management test page<\/a>. <\/p>\n\n\n\n

Because of the way WordPress works, it may or may not render the same way, depending on the size of the image.<\/p>\n\n\n\n

When an image is uploaded to the Media Library, often multiple lower res copies are created:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

In this case, I uploaded a file “PrimariesAdobeRGB.jpg”, which has profile Adobe RGB embedded. This is uploaded unaltered (marked with an arrow) to a location such as “http:\/\/simongarrett.uk\/simon\/wp-content\/uploads\/2021\/02\/PrimariesAdobeRGB.jpg<\/a>“. The Media Library also created three lower res versions, shown immediately above. To save space, it removes all<\/em> metadata, including the colour profile from these lower-res versions! These files have no metadata, so browsers will (or should, according to WWW) interpret them as sRGB. So why didn’t the Media Library convert them to Adobe RGB?????? I could guess, but to write it down would be gross defamation to the WordPress developer team!<\/p>\n\n\n\n

The Image Blocks below are displayed with html code like:<\/p>\n\n\n\n

<img ... src=\"http:\/\/simongarrett.uk\/simon\/wp-content\/uploads\/2021\/02\/PrimariesProPhotoRGB.jpg\" ...\n\nsrcset=\"https:\/\/simongarrett.uk\/simon\/wp-content\/uploads\/2021\/02\/PrimariesProPhotoRGB.jpg 1024w, https:\/\/simongarrett.uk\/simon\/wp-content\/uploads\/2021\/02\/PrimariesProPhotoRGB-300x200.jpg 300w, https:\/\/simongarrett.uk\/simon\/wp-content\/uploads\/2021\/02\/PrimariesProPhotoRGB-768x512.jpg 768w\"\n ...><\/code><\/pre>\n\n\n\n
It gives the source (“src” tag) as the original file (with the profile), but with alternatives (“srcset” tag) that can be used by the browser, depending on the size of the display window. These alternatives have no profile embedded.<\/em> <\/p>\n\n\n\n
What happens depends on the browser.  As of today (6th May 2025) some browsers note the src and srcset tags, and take the metadata and profile from the src= image, even when one of the smaller srcset= images are used.  Microsoft, infamous for its (mis)handling of colour management, seems to get very confused and its Edge browser seems to give up and mis-renders at any image size.<\/p>\n\n\n\n
This leaves users a few reliable options for posting images in colour spaces other than sRGB to the a WordPress website:<\/p>\n\n\n\n
    \n
  • Manually create <img > tags that explicitly reference the original uploaded image (which has an embedded profile), rather than use Image or other blocks that may uses alternative versions of the image with no profile.<\/li>\n\n\n\n
  • Use a gallery plugin with known good behaviour for colour profiles<\/li>\n\n\n\n
  • Host images on an external service with known good behaviour for colour profiles (e.g. flickr) and use a suitable plugin to embed images from that external service.  <\/li>\n<\/ul>\n\n\n\n
    Or upload only sRGB images.<\/p>\n\n\n\n
    sRGB<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    <\/div>\n\n\n\n
    AdobeRGB<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    <\/div>\n\n\n\n
    ProPhoto RGB<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    <\/div>\n\n\n\n
    End text<\/p>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    Test page to experiment with WordPress maltreatment of colour information. Updated 6th may 2025 This page should render the colour blobs below the same as on the Colour management test page.  Because of the way WordPress works, it may or may not render the same way, depending on the size of the image. When an […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":32,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"ngg_post_thumbnail":0,"footnotes":""},"class_list":["post-114","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/pages\/114","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/comments?post=114"}],"version-history":[{"count":16,"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/pages\/114\/revisions"}],"predecessor-version":[{"id":3906,"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/pages\/114\/revisions\/3906"}],"up":[{"embeddable":true,"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/pages\/32"}],"wp:attachment":[{"href":"https:\/\/simongarrett.uk\/simon\/wp-json\/wp\/v2\/media?parent=114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}