All updates
Platform

Sensible limits on names and folders

Names and folder names are now checked against what your storage provider will actually accept, and refused clearly here rather than failing somewhere downstream.

Every text field that names something — credentials, servers, jobs, groups, drives, folders — now has a limit, and says so when you cross it.

Two different kinds of limit, for two different reasons:

  • Your provider's rules. Amazon S3 caps an object key at 1,024 bytes; Linux filesystems cap a single folder or file name at 255. Exceeding either used to produce an error from the provider, several steps away from the box you typed in. BucketPilot now checks first and names the field.
  • Ours. Display names are capped at 100 characters — generous for a name, short enough that lists and tables stay readable.

Limits are measured in bytes where the provider measures bytes. This matters more than it sounds: Arabic, Chinese, Japanese and emoji characters take two to four bytes each, so a folder name that looks comfortably short can exceed a filesystem's limit. The message tells you the actual size and the actual limit, and mentions when non-Latin characters are the reason.

Folder names are also checked for the things that would quietly put your files somewhere else — slashes, .., and invisible control characters.