Repository navigation
Conversation
Craft 6 stores transforms below a _{volumeUid}/ folder and the upgrade
clears the transform index, so describe how to move existing transform
folders and how Craft picks them up again.
Related: craftcms/cms#20588
Amp-Thread-ID: https://ampcode.com/threads/T-01a1c75f-81cb-7691-a8d8-f4023e7fe794
Co-authored-by: Amp <amp@ampcode.com>
✅ Deploy Preview for craft-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Amp-Thread-ID: https://ampcode.com/threads/T-01a1c75f-81cb-7691-a8d8-f4023e7fe794 Co-authored-by: Amp <amp@ampcode.com>
This was referenced Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Copy, please review and rewrite as necessary
Description
Adds an Image Transforms step to the Craft 6 upgrade guide, after Run Migrations. The upgrade clears the transform index, and Craft 6 stores transforms below a
_{volumeUid}/folder, so every Craft 5 transform is regenerated. The new step explains how to move the existing transform folders so Craft reuses them.Evidence
Each claim in the section was checked against
craftcms/cms6.x:ImageTransformer::getTransformBasePath()returns'_'.$volume->uid.'/'.$folderPath. Craft 5's version returns{transformSubpath}/{folderPath}. Both are relative to the transform disk's root, not the volume's subpath.getTransformString(),getTransformSubfolder()and the transform filename produce the same names in Craft 5 and 6, including the/{assetId}subfolder used when the format changes.getTransformUrl()checks the disk, finds a moved file that isn't stale, and records it, so its URL is returned directly.generateTransformedImage()returns early when the file already exists and is newer than the transform's last change, so the image isn't processed again.immediately: the GraphQLimmediatelyargument and named transforms keeping their_handlefolder ship with the fix for [6.x]: Upgrade discards the transform index, and GraphQL named transforms lose their handle (all transforms regenerate to new paths) cms#20588. On 6.0.0-beta.1, GraphQL named transforms look for the parameter-based folder name instead, so this section should go out with that release.Related issues