# How to save Project with new name? **URL:** \ **Category:** Help\ **Created:** [January 26, 2026, 12:39am UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990 "2026-01-26T00:39:41Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Tenderfoot](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@Tenderfoot](https://librepcb.discourse.group/u/Tenderfoot)\ **Post date:** [January 26, 2026, 12:39am UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/1 "2026-01-26T00:39:41Z")
How do I save a project with a new name. For example saving ‘My Project’ as ‘My Project v2’ I’ve tried several ways, nothing works. Exporting as an ippz archive sort of works but I can’t rename it, it’s read-only and can’t be saved. Obviously I’m missing something. ---
**Author:** ![sasmus](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@sasmus](https://librepcb.discourse.group/u/sasmus)\ **Post date:** [January 26, 2026, 4:00pm UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/2 "2026-01-26T16:00:35Z")
I’m not sure if there is a better way in the newer versions of LibrePCB, but you could try this one: > [@Cloning a project, there's no "save as"](https://librepcb.discourse.group/t/cloning-a-project-theres-no-save-as/452): > > How do I do the equivalent of “save as” to make a new version of a whole project? Can I just duplicate the project folder and rename it or will that cause lower level conflicts? ---
**Author:** ![Tenderfoot](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@Tenderfoot](https://librepcb.discourse.group/u/Tenderfoot)\ **Post date:** [January 26, 2026, 5:27pm UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/3 "2026-01-26T17:27:00Z")
Thanks for your reply Sasmus. Yes I had read that post but it doesn’t seem to work for me. I get a message like ’There is no project in this folder’ (probably not the exact words). Also the poster asked if that method would cause conflicts, which wasn’t answered. ---
**Author:** ![ubruhin](https://avatars.discourse-cdn.com/v4/letter/u/c89c15/32.png) [@ubruhin](https://librepcb.discourse.group/u/ubruhin)\ **Post date:** [January 26, 2026, 5:31pm UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/4 "2026-01-26T17:31:04Z")
Sorry for the late reply. It’s unfortunately correct that this is still not supported yet, I hope we can implement such a feature soon. The cleanest way to copy a project is still [Cloning a project, there's no "save as" - #6 by grubernd](https://librepcb.discourse.group/t/cloning-a-project-theres-no-save-as/452/6). But it’s really not that bad to just copy a whole projects directory, it shouldn’t cause real troubles. The \*.lpp file inside the directory can be renamed as desired. > [@Tenderfoot](#): > > I get a message like ’There is no project in this folder’ (probably not the exact words). Sounds like the hidden file `.librepcb-project` was not copied. ---
**Author:** ![Tenderfoot](https://avatars.discourse-cdn.com/v4/letter/t/eb9ed0/32.png) [@Tenderfoot](https://librepcb.discourse.group/u/Tenderfoot)\ **Post date:** [January 26, 2026, 5:32pm UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/5 "2026-01-26T17:32:52Z")
No problem ubruhin, I think you are a busy man! I’ll try copying the file again and look for that hidden file 🙂 Perfect, hidden files were the problem it seems. Thanks again. ---
**Author:** ![giancarlo64](https://yyz2.discourse-cdn.com/free1/user_avatar/librepcb.discourse.group/giancarlo64/32/296_2.png) [@giancarlo64](https://librepcb.discourse.group/u/giancarlo64)\ **Post date:** [January 27, 2026, 7:33pm UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/6 "2026-01-27T19:33:08Z")
Hi, when I create a new version of a PCB, I usually start by copying the project folder and renaming it. For example, from **Baseboard\_V1.00** to **Baseboard\_V1.10** Then, in the new folder, I rename the _.lpp_ file accordingly, for example from **Baseboard\_V1.00.lpp** to **Baseboard\_V1.10.lpp** After that, I delete all the files in the _output_ subdirectory. Next, I open the new project and, from **Project → Setup** , I update the project version to the new one (e.g. **V1.10** ). Finally, I open the PCB project and update the printed information directly on the PCB. I usually place this information on the copper layer (top or bottom); if there is not enough space, I write the PCB information on the _Names_ layer. I don’t know if there is better way ---
**Author:** ![ubruhin](https://avatars.discourse-cdn.com/v4/letter/u/c89c15/32.png) [@ubruhin](https://librepcb.discourse.group/u/ubruhin)\ **Post date:** [January 27, 2026, 8:12pm UTC](https://librepcb.discourse.group/t/how-to-save-project-with-new-name/990/7 "2026-01-27T20:12:03Z")
> [@giancarlo64](#): > > when I create a new version of a PCB, I usually start by copying the project folder and renaming it. Honestly my recommended workflow for new versions is to keep working on the same project, not creating a new project for every revision. But I always add a \*.lppz output job, so in the output directories there is always a full copy of every old revision, which can be opened (read-only) in LibrePCB. For example: ``` output/v1.1/my-project-v1.1.lppz output/v1.2/my-project-v1.2.lppz output/v1.3/my-project-v1.3.lppz ``` So the workflow is: 1. Before ordering a PCB, run all output jobs to generate production data (including \*.lppz archive) 2. Afterwards, increment the projects version number 3. Continue working on the project until the next revision is complete 4. Repeat steps 1. to 3. So a copy of a project is never needed (respectively the \*.lppz output job automatically creates the copy for you). > [@giancarlo64](#): > > Finally, I open the PCB project and update the printed information directly on the PCB. > I usually place this information on the copper layer (top or bottom); if there is not enough space, I write the PCB information on the _Names_ layer. I recommend to set the text to `{{VERSION}}`, so it is always up-to-date and doesn’t need to be updated manually when the version number changes.