Pixillion doesn't have that capability. AI, though not always 100% accurate, suggests these workaround...
"Workaround Strategies
<span><span>touch</span><span> -r input.jpg output.jpg </span></span>
This sets the output file's timestamps to match those of the input file.
Batch Usage Example
After conversion, for each output file, issue:
powershell
<span><span>(</span><span>Get-Item</span><span> output</span><span>.</span><span>jpg</span><span>)</span><span>.</span><span>LastWriteTime = </span><span>(</span><span>Get-Item</span><span> input</span><span>.</span><span>jpg</span><span>)</span><span>.</span><span>LastWriteTime </span></span>
Linux/macOS:
bash
<span><span>touch</span><span> -r input.jpg output.jpg </span></span>
This workflow aligns the output file's modification date with that of the input file.
Metadata vs. Filesystem Date
Pixillion offers metadata management—preserving or editing tags within the image file—but does not provide filesystem-level timestamp controls within its GUI or CLI.
If this feature is crucial, external automation (batch scripts or additional tools) will be necessary after conversion.
In summary: Pixillion does not directly support copying the input file’s modification date to the output file during conversion; use external tools to achieve this result."