
You already own the objects. You want a stack of them in a different folder.
file.rocks is the UI. Everything stays in the bucket you connected.
This is bulk Move. It is not a single-file move. How to move a file to a folder in your own bucket is one row. How to move a folder in your own bucket is one folder row. This path is the selection toolbar.
If the destination folder is missing, that is how to create a folder in 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 bucket you own.
Check one or more file or folder rows. Or use the header checkbox (Select all files). The toolbar shows {N} selected.
Click toolbar Move.
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).
The toast is Moving N item(s)... then Moved N item(s) to {folder}. Root shows ... to /. If only some succeed, you get Moved X of N item(s) to {folder}. A full fail toasts Failed to move items.
The objects are rekeyed in the connected bucket. You are not copying them into file.rocks storage.
The toasts say item and items on purpose. Checked folders ride along with files.
Same MoveModal as the single-file and single-folder guides. Different entry: the selection toolbar, not a row menu.
Under the hood, files rekey like a rename into a new prefix. Folders use the folder-move path. Your provider still sets the object limits.
Keep the bucket paid. The stack is still yours. It just lives under a different prefix.
Need one file only? That is how to move a file to a folder in your own bucket.
Need one folder only? That is how to move a folder in your own bucket.
Need a different name on a file? That is how to rename a file in your own bucket.
Need files on the laptop first? That is how to upload files to your own bucket.