Transfigure’s iPad version saves user presets to iCloud Drive only after iCloud synchronization is switched on in the app’s settings. The feature starts disabled, so saving a preset on the tablet does not automatically create a shared desktop copy until you enable it.
For anyone using Transfigure preset syncing on iPad, the useful detail is where the automation stops. An iPad preset can reach iCloud Drive automatically, but Transfigure does not silently place that file into the desktop preset library. You still move the preset into the folder the desktop version actually reads.
On macOS, the desktop User folder sits under ~/Documents/Sugar Bytes/Transfigure/Presets/User. Moving an iPad preset to the Mac therefore means copying the file from the iCloud Drive User folder into that local Transfigure User folder. Going the other way means copying or dragging the desktop preset into iCloudDrive/Transfigure/Presets/User, after which it should appear in the iPad preset browser.
Windows needs a small translation because Sugar Bytes’ iPad instructions show a Unix-style desktop path. The desktop manual places Transfigure’s preset data under the user’s Documents\Sugar Bytes\Transfigure area on Windows. Open the folder from Documents rather than trying to paste the macOS path into File Explorer.
The distinction matters because the word sync can make the process sound more automatic than it is. iCloud handles the shared storage side, while the desktop library still expects presets in its own Documents location. Treat iCloud Drive as a transfer shelf between the two versions, and the workflow becomes much less confusing.
Transfigure does not need a special export package for this iPad-to-desktop handoff. The saved preset file itself is what you copy. Once a desktop preset lands in the iCloud Drive User folder, the iPad version is designed to expose it inside its User preset area without making you rebuild the patch by hand.
The reverse trip has one extra practical checkpoint. Seeing an iPad preset inside iCloud Drive proves the cloud copy exists, but it does not prove the desktop plug-in is reading it. If the preset is visible in Files or Finder yet missing from Transfigure on the computer, check whether the file was also copied into the desktop Transfigure preset directory.
Avoid renaming the main folders while troubleshooting. Sugar Bytes gives Transfigure a specific Presets and User hierarchy, and the app expects its files in that structure. A preset placed beside the User folder may be perfectly intact while remaining invisible to the browser.
Keep transferred presets directly inside the User folder when you want dependable visibility on iPad. A desktop folder structure may feel tidier, especially if you build many variations, but nested folders should not become part of the cross-device method unless Sugar Bytes changes the implementation.
The same limitation makes filenames more important. Clear names let you distinguish a finished patch from a revision without depending on folders the iPad side cannot read. If you keep several versions, use short descriptive suffixes and move only the versions you actually want available on both machines.
Preset syncing also remains separate from DAW project recall. AUv3 hosts can save Transfigure parameters and presets with their own sessions, while iCloud preset sharing is for moving saved user presets between devices. A project can therefore reopen with its Transfigure state even when you have not copied that preset into the shared User folder.
If a newly transferred file fails to appear, check the simple boundaries first. Confirm iCloud is enabled inside Transfigure, verify the file is directly inside the shared User folder, and make sure the desktop copy sits in Transfigure’s own Documents location. Those three checks match the way Sugar Bytes currently separates cloud storage, local preset storage, and the browser itself.
For anyone using Transfigure preset syncing on iPad, the useful detail is where the automation stops. An iPad preset can reach iCloud Drive automatically, but Transfigure does not silently place that file into the desktop preset library. You still move the preset into the folder the desktop version actually reads.
The iCloud folder is a bridge between two libraries
Once iCloud synchronization is enabled in Transfigure, presets saved on iPad are written into iCloudDrive/Transfigure/Presets/User. The folder is the handoff point. It is not the same location used by the desktop plug-in when it scans its own User presets.On macOS, the desktop User folder sits under ~/Documents/Sugar Bytes/Transfigure/Presets/User. Moving an iPad preset to the Mac therefore means copying the file from the iCloud Drive User folder into that local Transfigure User folder. Going the other way means copying or dragging the desktop preset into iCloudDrive/Transfigure/Presets/User, after which it should appear in the iPad preset browser.
Windows needs a small translation because Sugar Bytes’ iPad instructions show a Unix-style desktop path. The desktop manual places Transfigure’s preset data under the user’s Documents\Sugar Bytes\Transfigure area on Windows. Open the folder from Documents rather than trying to paste the macOS path into File Explorer.
The distinction matters because the word sync can make the process sound more automatic than it is. iCloud handles the shared storage side, while the desktop library still expects presets in its own Documents location. Treat iCloud Drive as a transfer shelf between the two versions, and the workflow becomes much less confusing.
Manual copying keeps the desktop side predictable
A clean routine is to finish the preset on one device, save it, then move that saved file across before editing it elsewhere. Editing separate copies of the same preset on two devices is asking a synchronization service to decide which version deserves to survive, and conflict handling in cloud file synchronization can produce competing versions or unexpected resolution behavior.Transfigure does not need a special export package for this iPad-to-desktop handoff. The saved preset file itself is what you copy. Once a desktop preset lands in the iCloud Drive User folder, the iPad version is designed to expose it inside its User preset area without making you rebuild the patch by hand.
The reverse trip has one extra practical checkpoint. Seeing an iPad preset inside iCloud Drive proves the cloud copy exists, but it does not prove the desktop plug-in is reading it. If the preset is visible in Files or Finder yet missing from Transfigure on the computer, check whether the file was also copied into the desktop Transfigure preset directory.
Avoid renaming the main folders while troubleshooting. Sugar Bytes gives Transfigure a specific Presets and User hierarchy, and the app expects its files in that structure. A preset placed beside the User folder may be perfectly intact while remaining invisible to the browser.
Subfolders are the limitation most likely to trip you up
Transfigure’s iPad manual explicitly warns that creating and then reading a subfolder in this shared preset workflow is not technically supported. Custom organization inside the synced User directory can therefore work against the preset browser instead of making a large collection easier to manage.Keep transferred presets directly inside the User folder when you want dependable visibility on iPad. A desktop folder structure may feel tidier, especially if you build many variations, but nested folders should not become part of the cross-device method unless Sugar Bytes changes the implementation.
The same limitation makes filenames more important. Clear names let you distinguish a finished patch from a revision without depending on folders the iPad side cannot read. If you keep several versions, use short descriptive suffixes and move only the versions you actually want available on both machines.
Preset syncing also remains separate from DAW project recall. AUv3 hosts can save Transfigure parameters and presets with their own sessions, while iCloud preset sharing is for moving saved user presets between devices. A project can therefore reopen with its Transfigure state even when you have not copied that preset into the shared User folder.
If a newly transferred file fails to appear, check the simple boundaries first. Confirm iCloud is enabled inside Transfigure, verify the file is directly inside the shared User folder, and make sure the desktop copy sits in Transfigure’s own Documents location. Those three checks match the way Sugar Bytes currently separates cloud storage, local preset storage, and the browser itself.
