Support
Help with Local File Diet
Questions about how compression behaves, bug reports, or anything about privacy — here is how to reach a human.
Contact
Bug reports
Open a GitHub issue Best for reproducible bugs and feature requests. Issues are public — never attach private documents or screenshots containing personal data. github.com/simo-hue/Local-File-DietCommon questions
Before you write in.
Why did my file barely get smaller?
Some files are already compressed as far as they usefully go — an H.264 video exported at a low bitrate, or a PDF that is mostly text, has little left to remove.
When a target is not reachable without visible damage, the app says so rather than producing a file that looks broken.
Are my files uploaded anywhere?
No. Compression runs on your iPhone. There is no server involved, and the app works with no network connection at all.
Files leave the device only when you choose to share, save or export the result yourself.
Will the app change my original file?
No. Local File Diet copies your selection into a temporary workspace and writes a new compressed file. The original is left exactly as it was.
Why can a compressed PDF lose selectable text?
Aggressive PDF compression can rebuild pages as flat images, which is sometimes the only way to hit a small target on a scanned document.
The app warns you before taking that route, because it also removes links, form fields and annotations.
How do I remove local data?
Clear temporary files from the app settings, clear recent history from the home screen, and delete any exported files wherever you saved them.
Deleting the app removes everything it stored on the device.
Is there a subscription?
No. Local File Diet is a one-time purchase with no subscription, no account and no in-app purchases. Every feature is unlocked from the start.