
You already own the file. You want it in a different folder.
file.rocks is the UI. The object stays in the bucket you connected.
This is a move. It is not a rename. How to rename a file in your own bucket changes the name in place. This path rekeys the object into another folder prefix in the same bucket.
If you need the folder first, that is how to create a folder in your own bucket. If the file is still on the laptop, that is how to upload files to your own bucket.
You need S3-compatible object storage. Not another Drive clone.
If you do not have a bucket hooked up, follow how to connect a Backblaze B2 bucket and come back. For the price table, see the cheapest cloud object storage comparison.
Sign in at file.rocks. Open Files. Pick a file you own.
Open the file row menu. Choose Move to folder.
The modal title is Move to /. While you browse it is Move to /current-folder. Click a folder to go in. .. goes up.
Click Move (or Cancel). Move stays disabled while the destination is the folder the file is already in.
The toast is Moving file... then Moved to {folder}. Root shows Moved to /. The object is rekeyed in the connected bucket. You are not copying it into file.rocks storage.
The name stays the same. Only the folder prefix changes. Same rename API under the hood. Different job.
A failed move toasts Failed to rename file.
Folder-row Move and bulk toolbar Move are later posts.
The objects stay in your bucket. Your provider sets the object limits.
Keep the bucket paid. The file is still yours. It just lives under a different prefix.
Need a different name instead? That is how to rename a file in your own bucket.
Need a folder to drop it in? That is how to create a folder in your own bucket.
Need a link you can send? That is how to share a file from your own bucket.
Need a whole folder link? That is how to share a folder from your own bucket.