> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/project-and-publishing/syncing-projects.md). # Syncing Projects Sync Elements projects across multiple Macs If you want to work on your Elements project across multiple Macs, we recommend using iCloud Drive. It’s built into macOS, fast, and well-integrated with the system, making it the most reliable option for syncing your projects. While some users have reported success using services like Google Drive, we’ve also seen cases where those services can cause sync issues or corrupt project files due to the way they handle file locking and syncing. #### Tips for iCloud Drive * Make sure iCloud Drive is enabled on both Macs. * Store your .elements project file inside your iCloud Drive folder. * Wait for the project to finish syncing before opening it on another machine. #### Supported Sync Services * ✅ iCloud Drive * ❌ Google Drive * ❌ Dropbox Avoid opening the same project on both Macs at the same time. Always allow iCloud to finish syncing before making changes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.realmacsoftware.com/elements-docs/using-elements/project-and-publishing/syncing-projects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.