Hey, I’m quite new in this topic, so sorry, if I’m using the wrong channel.
My problem is, when I add a photo to a new created point, the photo will remain in the cloud even if I delete the spatial created point. Is there any chance to delete photos in the cloud? It is not possible, rather through the website or the app.
Wish you all best!
Imported from GitHub discussion by @UlfEichelquetscher on 2023-04-15T15:48:29Z
hello,
you can delete the files locally and synchronize your project from qgis (with the ‘prefer local’ option selected). It will then delete the files from the cloud that aren’t present locally anymore.
hopefully this helped 
Imported from GitHub comment by @babakou9 on 2023-04-20T21:59:25Z
This is not necessarily the case… I recently changed a base layer from raster GPKG to TIFF and removed the GPKG from project in QGIS and from local directory. I also deleted another GPKG vector layer from project at same time. When I synchronized the system did not remove the deleted local files from the cloud. They persisted and cannot be removed through web UI, I guess since they are the only version. The only way I could delete them was by using the qfieldcloud-sdk CLI.
Imported from GitHub comment by @wanderingnature on 2023-04-21T03:28:04Z
Hello, I’m having a similar issue as well. I’ve deleted all features in the QField app, and synchronized changed changes with my desktop. My Desktop DCIM folder is empty, but all historic photos are persisting in the Qfield app, and I have no option to delete the photos in the project folder. I’m running IOS.
Imported from GitHub comment by @sheafile on 2024-11-21T18:19:08Z
sheafile A solution for you would be to delete the project on your device (upload changed features first). Then redownload - if the pictures are not on the cloud anymore (because you deleted them on the desktop and pushed this deletion to the cloud) it will only sync the pictures which are in the cloud.
Imported from GitHub comment by @meyerlor on 2024-11-27T11:01:21Z
i ran in the same problem with PDFs created through QField - they are clogging the device space quite effectivly if you have an atlas with ~2000 features and a file for each one. I created an issue on the QField Ideas Platform - maybe you can upvote it there so the dev’s might look into it.
Imported from GitHub comment by @meyerlor on 2024-11-27T11:06:54Z
Absolutely sir, appreciate you passing your fix along! Seems like a pretty notable issue that should be patched…
Imported from GitHub comment by @sheafile on 2024-11-27T19:32:04Z
Here’s the solution: When printing layouts (atlas and non-atlas ones), place them in the current project path's subfolder for easier synchronization / export by nirvn · Pull Request #5852 · opengisch/QField · GitHub – as of QField’s next version (3.5), layouts will be written in the current project’s subfolder named ‘layouts’, which will allow for synchronization with QFC (provided layouts is added to the attachments directories list) and will make it easier to clear by using the delete project folder from the local files view’s 3-dot menu.
Imported from GitHub comment by @nirvn on 2024-11-28T02:39:46Z
