Archive File Naming Builder
Generate consistent archival filenames from collection, container, item and date fields and detect collisions.
- 1Explore the example
- 2Edit your assumptions
- 3Compare & export
Loading the worked example…
Your working data
Edit cells directly or import a CSV. Download “Input CSV” for the required column names. Up to 200 rows; scroll the table sideways for additional fields.
Detailed analysis
Exports include all results, regardless of the search filter. The HTML report includes assumptions and source data; use your browser’s Print command for PDF.
Chart shows the first 20 rows; negative values use a warm color. Click table headers to sort.
Compare up to four scenarios
Capture the current inputs, change assumptions and capture again. Scenarios are included in downloaded projects.
What this model includes
Produces names only; does not rename files. Non-ASCII characters and punctuation are converted to hyphens; review normalized names for lost distinctions.
Import and save safely
CSV imports use your current assumptions. Project files restore assumptions, rows and saved scenarios. No automatic saving: download a project before closing this page. Imports are limited to 10 MiB and 200 rows. Calculations run in your browser; the site’s advertising and analytics follow its privacy policy.
Using Archive File Naming Builder
Generate consistent archival filenames from collection, container, item and date fields and detect collisions.
- Review the preloaded example and the model limits before entering real data.
- Adjust item-number digits, letter case.
- Edit the collection rows or import a CSV using the Input CSV column template.
- Open Results & chart to inspect details, sort columns and filter rows.
- Capture alternative scenarios, then download a project, result CSV or printable report.
Example
The worked example includes History, History. Change the first item-number digits setting and compare the result with a saved baseline.
Questions & answers
What does Archive File Naming Builder calculate?
Generate consistent archival filenames from collection, container, item and date fields and detect collisions.
What are the important limitations?
Produces names only; does not rename files. Non-ASCII characters and punctuation are converted to hyphens; review normalized names for lost distinctions.
Can I continue my work later?
Yes. Save a project JSON file and reopen it with Import CSV / project. It contains the working data, assumptions and up to four scenarios. Nothing is saved automatically.
What CSV columns do I need?
collection, box, folder, item, date, extension. Download Input CSV for a compatible example. CSV imports keep your current assumptions.
Are these example figures current industry benchmarks?
No. They are illustrative values to demonstrate the model. Replace them with figures appropriate to your situation.
Related tools
A useful next step for your task.
Everyday CalculatorsLibrary Loan TrackerReview a small lending collection for overdue loans, upcoming returns and borrower-level follow-up.
Everyday CalculatorsLibrary Shelf Capacity PlannerEstimate shelf demand by collection type using average spine widths, growth and browsing space.
Everyday CalculatorsCollection Condition RegisterPrioritize collection inspections using recorded condition, handling frequency and inspection intervals.
Everyday Calculators2026 Tax Refund EstimatorEstimate your 2026 federal income tax refund or balance due with the new IRS brackets, standard deduction, tips, overtime, car-loan and senior…
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.