Archicad currently does not support saving and working on solo .PLN files directly within cloud-synced folders such as Dropbox, Google Drive, or OneDrive. The save operation generates temporary and lock files that conflict with real-time sync clients, creating a race condition that can result in save failures and, in rare cases, file corruption.
This is not a niche edge case. The majority of small and mid-size architecture firms in 2026 use cloud storage as their primary file management infrastructure. Telling users to avoid cloud-synced folders and instead work locally then manually copy files is not a realistic workflow. It introduces human error, breaks version continuity, and contradicts how every other professional desktop application in the industry operates. Adobe, AutoCAD, Vectorworks, Microsoft Office all handle cloud-synced folders without issue.
The request is straightforward: implement a save mechanism for solo .PLN files that coordinates with cloud sync clients, either by pausing sync during the save sequence, using atomic write operations, or adopting a save architecture compatible with how modern cloud storage hooks into the OS. The technical pattern is well established across the industry.
This is not a nice-to-have. For firms that rely on Dropbox or Google Drive as their file backbone, which is most small firms, this is a fundamental reliability gap that creates real data risk daily.
Open