Special character support and file path restrictions
Unsupported characters are removed from file names and paths before delivering the files
Different destinations have different rules when it comes to support for special characters in file names and file paths. MASV avoids disruptions to transfers by removing special characters that are defined in general and destination-specific guidelines. Any file path metadata in MASV-generated package or sidecar files is updated accordingly. Please see the details below.
General file path specifications for MASV
When files are uploaded to MASV, the following file path issues are addressed by MASV, regardless of which integration is set as the destination:
- Replace backslashes
\with forward slash/ - Remove relative path indicators (to escape the working folder). Example:
../ - Remove leading and trailing
/forward slashes. Example:/my/file.jpg/becomesmy/file.jpg. - Remove tabs and new line characters.
Supported characters and file path specifications for integrations
The guidelines below apply exclusively to files delivered to the specified integration.
Amazon S3
MASV supports most UTF-8 characters, including multilingual characters and an extensive list of special characters. For more information, see Object naming guidelines: Safe characters, Characters that might require special handling, and Characters to avoid (MASV makes a best effort at supporting as many of these characters as possible).
File path length limit is 1024 bytes.
Microsoft Azure Blob Storage
Azure integrations allow any characters or symbols, with the following exception:
-
Individual segments cannot end with a period
.Example:/my./files./go./here.jpgbecomesmy/files/go/here.jpg
For more information, see Naming and referencing containers, blobs, and metadata and Azure storage supported character scrubber.
Backblaze
Please refer to the Backblaze Help to ensure you follow file name rules and bucket name rules.
MIcrosoft OneDrive and Sharepoint
For information about invalid characters, file, and folder names in OneDrive and SharePoint, see Restrictions and limitations in OneDrive and Sharepoint.