Free, Pro and Business customers have a limit of 512 MB.- Default Cache Behavior
For Enterprise customers the default maximum cacheable file size is 5 GB. Contact your account team to request a limit increase.
AA
IIAIAIAIAAAIIIAAAIA
IIAIAIIA
E
OE
K
C
bin.føø.com (bin.xn--f-5gaa.com).O
HO
Dsomefile#123.jpg and I upload it via R2 dashboard, it shows as being uploaded as somefile, but accessing it via a URL encoded string (needed since anything after # isn't sent to the server by the browser). So the R2 upload process drops anything after the # (same as a browser would do making the request for it). At which point you would be left with an empty file.Dsomefile#123.jpg ended up as somefile in the dashboard. I was too scared to try it with a file that started with # because I didn't want to end up an object that wasn't deletable. 
D# in it, so it's not the only place in the world that works that way, but uploading to R2 isn't a normal browser request. Might be something like they are parsing the uploaded R2 object key as a URL path, and if it's a URL path, anything after # would be dropped. It does seem like a bug to me.DD
DPUT https://{account_id}.r2.cloudflarestorage.com/{bucketname}/{object_key}# isn't valid in an HTTP request.Dbin.føø.com (bin.xn--f-5gaa.com)somefile#123.jpgsomefile#123.jpgsomefilesomefile####PUT https://{account_id}.r2.cloudflarestorage.com/{bucketname}/{object_key}