Free tool · no limit · nothing is uploaded
Batch converter
A whole preset pack in one pass. Drop the folder, pick the output, get one archive back — with no cap on how many files and no account.
Drop a folder’s worth of presets or LUTs
.xmp, .lrtemplate, .cube or .3dl — as many as you like, no limit and no account. Everything is converted on your own machine.
What converts to what
| From | To | Fidelity |
|---|---|---|
| .lrtemplate | .xmp | Exact — the same setting names in a different syntax |
| .xmp / .lrtemplate | .cube · .3dl | Exact for the global grade; masks and vignettes cannot exist in a LUT |
| .cube | .3dl | Exact apart from 12-bit quantisation, with the entry order transposed |
| .cube | .xmp | Approximate — curves exact, colour estimated |
The last row is the only lossy one, and it is lossy for a structural reason rather than a fixable one: a 33³ LUT holds 35,937 independent values and a Lightroom preset holds roughly sixty parameters. For one file, CUBE to XMP renders both and reports the measured error. A batch cannot show you that per file, so it warns instead.
Why it stays free
Batch conversion is the obvious thing to charge for — somebody with a two-hundred-preset pack has a real problem worth real money. It is free anyway, and uncapped, because the conversion costs us nothing: it happens on your machine, not on a server we rent. There is no per-file cost to pass on, so metering it would be a toll booth on an empty road.
Frequently asked questions
Is there a limit on how many files I can convert?
No. There is no cap, no queue and no paid tier. The conversion runs on your own machine rather than on a server, so there is no cost to meter — the only real limit is your own memory and patience.
How long does a large batch take?
Converting a preset to a LUT means a real render per file, so it is the slow direction: roughly a third of a second each at 33³, and around a second at 65³. Two hundred presets is therefore about a minute at the default size. The page estimates it before you start and shows per-file progress rather than an indeterminate spinner. Preset-to-preset and LUT-to-LUT conversions are near-instant.
Are my files uploaded?
No. Every file is read with the browser's File API, converted on your own CPU and GPU, and packed into an archive locally. Nothing is transmitted, and the page keeps working with the network disconnected once loaded.
What happens if one file is corrupt?
It is skipped and named in the summary afterwards, and the rest still convert. An archive that silently contains fewer files than you dropped is worse than one that tells you which three failed.
Can I mix presets and LUTs in one batch?
Yes. Drop whatever you have — the tool detects each file's type. When the batch is mixed, the output options are the ones that make sense for everything in it.
Why is converting LUTs to presets marked as approximate?
Because it is. A 33³ LUT holds 35,937 independent colour values; a Lightroom preset holds roughly sixty parameters, so most LUTs are not expressible as one. Tone curves are extracted exactly and colour is estimated. For a single file the CUBE to XMP tool renders both and reports the measured error — a batch cannot show you that for every file, which is why it says so up front instead.
You have the preset. Do you know what it does?
A preset is sixty numbers, and most of them barely matter. Drop the photo and its sidecar into the Studio and the edit replays in six stages — light, curves, colour, masks, finish — so you can see which decision actually carried the look rather than guessing from the finished frame.