Revit PDF Naming Rules: Sheet Number, Sheet Name and Custom File Names
Revit PDF naming rules can build filenames from sheet parameters instead of forcing users to rename dozens of files after export.
Beginner takeaway: Use stable parameters first—usually Sheet Number—then readable fields such as Sheet Name.
What you need to understand first
A good naming rule supports sorting, uniqueness and revision/document-control needs without depending on manual edits.
- Native PDF Export supports configurable naming rules for multiple exported files.
- Naming rules can use Revit parameters.
- Manual naming is still available for single/combined exports.
Related guides: Revit Export Separate PDFs: One File per Sheet, AutoCAD Sheet Set PDF File Naming: A Practical Workflow, and Revit View/Sheet Sets for Printing: Save and Reuse Sheet Selections.
Step-by-step workflow
Step 1 — Define document-control format
Where: Project standard
Do this: Write the filename pattern before configuring Revit.
Check: Everyone agrees on expected output.
Step 2 — Open naming rules
Where: PDF Export > File Name > naming rules
Do this: Open the rule setup.
Check: Parameters are available.
Step 3 — Add stable parameters
Where: Naming rule
Do this: Put Sheet Number before descriptive fields.
Check: Files sort predictably.
Step 4 — Test edge cases
Where: A few sheets
Do this: Check long names, special characters and duplicate descriptions.
Check: Rule remains unique and usable.
Step 5 — Export clean set
Where: Issue folder
Do this: Generate files and compare with register.
Check: Names require no manual cleanup.
What usually goes wrong
| What you see | Likely layer | First check |
|---|---|---|
| Duplicate filenames | Rule lacks unique field | Add Sheet Number. |
| Files sort badly | Name starts with description | Lead with sortable identifier. |
| Illegal characters | Sheet parameter content | Clean project naming values. |
| Revision naming inconsistent | No policy | Define whether revision belongs in file name. |
Practical example
For sheet `A101` named `Floor Plan – Level 1`, a rule such as `A101-Floor Plan – Level 1.pdf` is readable and sortable. If the project requires revision in the filename, add it according to one documented rule rather than typing it manually after export.
What not to do
- Do not depend on Sheet Name alone for uniqueness.
- Do not build a rule from unstable descriptive parameters that change late in the project without considering revision control.
- Do not manually rename a large export unless the software cannot express the required rule.
Good office standard
Keep one naming standard per deliverable and test it on cover sheets, typical sheets and unusually long names before production.
Quick verification before you move on
- Use one representative drawing or sheet, not a production batch.
- Verify page size, orientation and a known dimension.
- Compare Preview/PDF with the physical output when a printer is involved.
- Save the setting or set only after the result is repeatable.
Official references
Frequently asked questions
Can Revit name PDFs automatically?
Yes. Native PDF Export supports naming rules based on selected parameters.
Which parameter should come first?
Sheet Number is usually the most stable and sortable identifier.
Should revisions be included?
Only if the project’s document-control rule requires them; be consistent.
Explore more in Revit Printing & PDF Guide.