# Tool to solve hardcoded/broken paths when moving RapidWeaver projects across Macs **URL:** \ **Category:** RapidWeaver Classic\ **Tags:** stacks, rapidweaver\ **Created:** [October 2, 2026, 11:39pm UTC](https://forums.realmacsoftware.com/t/tool-to-solve-hardcoded-broken-paths-when-moving-rapidweaver-projects-across-macs/57763 "2026-10-02T23:39:16Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![jabraham](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@jabraham](https://forums.realmacsoftware.com/u/jabraham)\ **Post date:** [October 2, 2026, 11:39pm UTC](https://forums.realmacsoftware.com/t/tool-to-solve-hardcoded-broken-paths-when-moving-rapidweaver-projects-across-macs/57763/1 "2026-10-02T23:39:16Z")
You guys, I love RapidWeaver Classic, but my projects always ended up with fixed/hardcoded paths in various pages, resources, or Stacks, so I could never open and edit my project on a different computer where drive names, usernames, or network paths were different. I’ve actually been struggling with this for several years! Anyway, I had my AI buddy Gemini help me write a Python tool to inspect, repair, and relocate path references—preferring to internalize them into the project bundle so the .rwc file becomes 100% self-contained and portable across any Mac. It seems to work, unlike all my previous attempts in this regard! It runs with any standard Python 3 installation on macOS (zero extra packages/dependencies needed). If anyone else is interested or finds it useful, please let me know — I’m not going to spend hours polishing it if I’m the only one using it, but check it out and if you find it useful I might be motivated to spend some more time on it. > **[GitHub - jeabraham/Remap\_Rapidweaver](https://github.com/jeabraham/Remap_Rapidweaver)** > > Contribute to jeabraham/Remap\_Rapidweaver development by creating an account on GitHub.