How to move or delete files safely
Move or delete files in the Files library without accidentally breaking existing post links, file fields, frontend code, or private delivery routes.
Use this guide when you need to reorganize or remove PDFs, documents, spreadsheets, archives, or other downloadable files from the Files library.
Moving a file changes its object path. Deleting a file removes the storage object. Deleting a folder removes everything inside it. BaseBuddy does not rewrite existing post links, file fields, frontend code, external references, or signed/private delivery routes after you move or delete files.
Before you move or delete files
Check where the file is linked before changing it. Look at post bodies, mapped file fields, previews, live pages, frontend code, and any external places where the file URL or object path may have been shared.
For production content, use a small safe process:
- Choose one file that is easy to verify.
- Move or delete that one file first.
- Open the affected post in BaseBuddy.
- Check the post preview or your site.
- Continue with the rest only after the reference still works or after you have updated the old reference yourself.
If your site stores file URLs or object paths in content, a move can leave the old value pointing at the old path. If you delete a file, any old reference to that file can become broken.

Move one file
- Open the project in BaseBuddy.
- Open Files.
- Browse or search for the file.
- Open File options on the file row.
- Choose Move file.
- In the Move file dialog, choose a Destination.
- Click Move file.
The file is moved to the destination folder. If another file already uses the same name there, BaseBuddy chooses a unique path.
After the move, check any post, file field, site page, frontend code, external reference, or private delivery route that used the old file path. BaseBuddy does not update those references for you.
Click Cancel if you opened the dialog and are not ready to move the file.
Delete one file
- Open Files.
- Browse or search for the file.
- Open File options on the file row.
- Choose Delete file.
- In Delete file?, review the file name.
- Click Delete file.
The file object is removed from file storage. Existing post links, file fields, frontend code, external references, and signed/private delivery routes are not rewritten. If something still points at that file, the download may break or fail to load.
Click Cancel if you are not sure the file is safe to remove.
Move a folder
Moving a folder changes the object paths for files inside it.
- Open Files.
- Open Folder options on the folder card.
- Choose Move folder.
- In the Move folder dialog, choose a Destination.
- Click Move folder.
You can also open the folder first and use Move Folder in the right sidebar.
If the destination already has a folder with the same name, BaseBuddy chooses a unique path. After the move, verify posts, file fields, site pages, frontend code, external references, and private delivery routes that used files from that folder. BaseBuddy does not scan and rewrite old links, paths, or delivery routes.
Click Cancel if you are not ready to move the folder.
Delete a folder
Deleting a folder removes the files and folder marker objects inside it.
- Open Files.
- Open Folder options on the folder card.
- Choose Delete folder.
- In Delete folder?, review the folder name and warning.
- Click Delete folder.
You can also open the folder first and use Delete Folder in the right sidebar.
BaseBuddy deletes the objects inside that folder from file storage. It does not rewrite existing post links, file fields, frontend code, external references, or signed/private delivery routes. Check affected posts and your site after deleting, especially if the folder contained files already used in published content.
Click Cancel if the folder may still be in use.
Verify after the change
After moving or deleting files:
- Reopen the affected post in BaseBuddy.
- Check body links and mapped file fields.
- Save only if you intentionally changed post content.
- Check your site or preview.
- Fix any old references that still point to moved or deleted paths.
Normal Save and Update still follow the saved mapping and write dirty mapped fields only. Moving or deleting files is a separate Files library action, not a hidden rewrite of post content.
If your files use private storage, treat generated URLs as temporary. Do not copy signed URLs into long-lived content, documentation, support tickets, or public screenshots.
Related guides
- How to upload and manage files in the Files library
- How to organize files with folders
- How to insert files or downloads into a post
- How to fix broken image or file URLs
- How to move or delete images safely
- Media and files
- Safe editing model