diff --git a/backend/crypt/crypt.go b/backend/crypt/crypt.go
index ce200801c..641d6642f 100644
--- a/backend/crypt/crypt.go
+++ b/backend/crypt/crypt.go
@@ -147,7 +147,7 @@ length and if it's case sensitive.`,
 				},
 				{
 					Value: "base32768",
-					Help:  "Encode using base32768. Suitable if your remote counts UTF-16 or\nUnicode codepoint instead of UTF-8 byte length. (Eg. Onedrive)",
+					Help:  "Encode using base32768. Suitable if your remote counts UTF-16 or\nUnicode codepoint instead of UTF-8 byte length. (Eg. Onedrive, Dropbox)",
 				},
 			},
 			Advanced: true,
diff --git a/docs/content/crypt.md b/docs/content/crypt.md
index 4a5eca211..bb2f58c3a 100644
--- a/docs/content/crypt.md
+++ b/docs/content/crypt.md
@@ -379,7 +379,7 @@ address this problem to a certain degree.
 For cloud storage systems with case sensitive file names (e.g. Google Drive),
 `base64` can be used to reduce file name length. 
 For cloud storage systems using UTF-16 to store file names internally
-(e.g. OneDrive), `base32768` can be used to drastically reduce
+(e.g. OneDrive, Dropbox), `base32768` can be used to drastically reduce
 file name length. 
 
 An alternative, future rclone file name encryption mode may tolerate