> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/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/classic/user-manual/troubleshooting/how-to-locate-your-addons-and-preferences.md). # How to Locate Your Addons and Preferences Locate addons, preferences, and projects This guide will show you how to locate RapidWeaver Addons, Projects, and Preferences. This is especially helpful if you're upgrading or moving to another Mac. ### How to Find and Backup Your Addons To locate your third-party Addons launch RapidWeaver, and open the **Preferences** window and go to the **Addons** Tab. You can then use the "**Reveal in Finder**" button to show the location of your addons. Alternatively there's an "**Export Addons Directory**" button that will export and zip your entire Addons directory. The "Export Addons Directory" option will ask for a location to save the "My Adons.zip" file. This is useful to back up your addons or move them to another Mac. ![](https://3941723260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQxK7JyV6iH6ddgHOOt8v%2Fuploads%2F3i7v3hjWgNH1BRLULMvT%2FCleanShot%202022-07-08%20at%203.56.01%402x.png?alt=media\&token=c76c655a-ff76-4395-9c74-b67b5cbe6ba1) ### How to Find Your RapidWeaver Preferences The RapidWeaver preferences are located in the following locations: `~/Library/Containers/com.realmacsoftware.rapidweaver8/Data/Library/Preferences/com.realmacsoftware.rapidweaver8.plist` `~/Library/Group Containers/P97H7FTHWN.com.realmacsoftware.rapidweaver8/Library/Preferences/P97H7FTHWN.com.realmacsoftware.rapidweaver8.plist` The license file(s) for RapidWeaver Classic are stored here (and also in the Keychain, search for DevAnt). `~/LibraryContainers/com.realmacsoftware.rapidweaver8/Data/Library/Application Support/RapidWeaver Classic/.licence` `/Users/Shared/RapidWeaver` (you can remove this folder) Press command-shift-g in the Finder and paste each of the above into the Field, and hit Return. This should take you to the exact location. ![](https://3941723260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQxK7JyV6iH6ddgHOOt8v%2Fuploads%2FIjysZJQkV7oddQ1VyA0M%2FCleanShot%202022-07-08%20at%203.51.21%402x.png?alt=media\&token=8744977b-e822-447c-8ca4-a2375972385d) ### How to Find Your Project Files You'll need to copy over your project file(s), this file or files (depending on how many websites you’ve created in RapidWeaver) are often stored somewhere in your Documents folder — the files would be in the location you chose when saving your projects.\ \ For example, we keep ours in \~/Documents/Website Projects/\ RapidWeaver Classic project files end with .rwc, and RapidWeaver element project files end with .rwe.\ \ Once you've found all your project files, you can copy them over to your new Mac. #### Don't forget about Project Resources By default, RapidWeaver is set to copy over any resources (files, images, etc) that you added to your project so you shouldn’t need to worry about this when moving projects to a new Mac.\ \ However, sometimes (if you chose) your project resources may be external, if that is the case make sure you copy over all images and files that your website may need. RapidWeaver will prompt you to locate these if it can't find them when you open your project. --- # 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/classic/user-manual/troubleshooting/how-to-locate-your-addons-and-preferences.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.