Repository navigation
Ability to convert HEIC to JPG #63754
Description
Tip
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
Is your feature request related to a problem? Please describe.
In an effort to improve auto-upload functionality on iOS, we plan to use the new API for iOS 27+ that allows us to upload photos/videos in the background faster and more reliably.
For this, however, we need to move the conversion of HEIC to JPG from client to server, as the new API does not allow asset modifications.
Describe the solution you'd like
Add the ability for server to convert a newly uploaded HEIC photo to a JPG. The conversion will be an optional toggle on the iOS app, so we can specify conversion with maybe a header field or some other param.
Describe alternatives you've considered
No alternatives.
Additional context
For the current HEIC to JPG conversion on client we use 0.85 JPG compression quality, so it should be the same on server:
let jpegData = CIContext().jpegRepresentation(
of: ciImage,
colorSpace: colorSpace,
options: [compressionQuality: 0.85]
)
Activity
artonge commentedon Aug 28, 2026
Linked to #58393
mpivchev commentedon Sep 21, 2026
nextcloud/ios#4288 JPEG compression quality is now 0.85
susnux commentedon Sep 21, 2026
But be have HEIC / HEIF now as previews? #64519
mpivchev commentedon Sep 22, 2026
It's for compatibility with 3rd party software, as some of them still don't support HEIC. Currently a user can decide if they want to convert HEIC to JPG, and we should keep that option supported.
naelfe commentedon Oct 2, 2026
little addition:
I did change it to reduce the size from 3x down to the former jpg size. 0.85 was a semi educated guess. It worked, but still is file size seems not be quite as low as before the changes. Now it's approx. at 1.2x instead of 3x (setting it to 0.8 might have been even better).
Fine for me since the process will be changed in the future. Making the value configurable in the iOS app does not seem to be needed if the transformation will be done by the server :)