Different components in Acquia DAM have specific character restrictions. The following guidelines separate restrictions by component type:
Best practices for filenames:
Use dashes (-) or underscores (_) to separate words.
Keep filenames to 27 characters or less (excluding extension) for optimal display.
Limit filename length to a maximum of 128 characters.
Ensure file extensions are present to process and match assets during imports and exports.
Avoid these in filenames:
Spaces at the start or end
Spaces before the file extension
Periods at the start or end
Files that end with .appl
The following characters: < > : " / \ | ? * , + % # ( ) [ ] { }
DOS-reserved filenames: AUX, CLOCK$, COM1-COM9, CON, LPT1-LPT9, NUL, PRN
Avoid these characters in collection and category names:
< > : " / \ | ? * , + % # ( ) [ ] { }
Spaces at the start or end
Character restrictions for metadata fields:
Avoid the following characters, which can cause issues with search or imports: < > : " / \ | ? * , + % # ( ) [ ] { }
System trims spaces at the start and end.
System can strip some special characters during process cycles.
The following items lack support across any component:
Certain Latin, Asian, and Arabic characters
Advanced mathematical symbols
Unicode characters that can cause system conflicts
< > : " / \ | ? * , + % # ( ) [ ] { }
Spaces at the start or end
Character restrictions for metadata fields:
Avoid the following characters, which can cause issues with search or imports: < > : " / \ | ? * , + % # ( ) [ ] { }
System trims spaces at the start and end.
System can strip some special characters during process cycles.
The following items lack support across any component:
Certain Latin, Asian, and Arabic characters
Advanced mathematical symbols
Unicode characters that can cause system conflicts
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.