Skip to content

"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files

docs: Document unsupported S3 object keys with double slashes

Adam Kasztennybe1fb99aeea3
diff --git a/docs/content/s3.md b/docs/content/s3.md
index a368a2a8d..0042215af 100644
--- a/docs/content/s3.md
+++ b/docs/content/s3.md
@@ -671,6 +671,20 @@ work with the SDK properly:
| . | . |
| .. | .. |
+#### Important note about double slashes (`//`)
+
+Object keys containing consecutive forward slashes (`//`) are **not supported** by rclone.
+
+When rclone encounters an object key with `//` (e.g., `a//b`), it will normalize the path to use a single slash (e.g., `a/b`). This normalization can cause "object not found" errors when trying to access the original object, as rclone will look for the normalized path instead of the actual object key.
+
+**Example:**
+- Original S3 object key: `folder//file.txt`
+- rclone interprets it as: `folder/file.txt`
+- Result: "object not found" error when trying to access `folder//file.txt`
+
+**Workaround:**
+Avoid using consecutive forward slashes (`//`) in S3 object keys when using rclone. If you have existing objects with `//` in their keys, you will need to rename them to use single slashes or access them through other means.
+
### Multipart uploads
rclone supports multipart uploads with S3 which means that it can