How it works: how your files are handled
Revit Downgrade converts a Revit file to an older Revit version. This page says what happens to your file and when it is deleted.
When your file is sent
The Revit version and the file type are read in your browser. Your file is only sent when you press Downgrade.
When files are deleted
| File | Deleted |
|---|---|
| An upload that was not finished | 1 hour after the last data arrived (6 hours at most) |
| A conversion you cancelled | Right away |
| Your original file | As soon as the conversion succeeds |
| The original of a failed conversion | Kept in a report for up to 7 days to fix the problem, or until you press Delete my file. A copy of a file that is already kept stays 15 minutes, or until you press Delete now. |
| The converted file and the list of removed elements | 2 hours after they are ready, or when you press Delete now |
| Reports (a failed conversion, or a file you sent because it does not open in Revit) | After 7 days, or when you delete it or ask, whichever comes first. At most 20 GB are kept; the oldest go first. The error message stays on the server for 90 days after the file is deleted, without the file name. |
When a converted file doesn't open in Revit
If Revit refuses a converted file, you can press "File doesn't open in Revit?" on the result. Nothing is sent unless you tick the consent box and press Send. Then the server keeps your original file (chosen again if the page no longer holds it), a copy of the converted file, the conversion log and your note, if you wrote one, as a report for up to 7 days, only to find and fix the problem. The report holds no file name and no network address; you get a report code to quote. A conversion reported this way counts as failed in the usage statistics.
Cookies and tracking
Revit Downgrade sets no tracking cookies and has no advertising. Page views are counted with Cloudflare Web Analytics, which uses no cookies and does not follow you across sites. Your browser keeps your language choice and a list of your unfinished uploads (file name, size and date with the conversion ID), only so that choosing the same file again can continue its upload. The list is cleared when an upload finishes and after 6 hours.
Usage statistics
The server keeps running totals: conversions that finished, files that still fail, failing files kept and waiting for a fix, files fixed, and the number of different visitors who converted a file. A visitor is recognised by a one-way, keyed hash of their network address (IPv6 addresses are grouped by /64 network), so the count is approximate: people who share a network count once, and a person who changes network may count twice. A file is recognised by a one-way, keyed hash of its content, so a failing file sent again counts once. The hash of a file that fails or does not open is kept until a conversion or a check in Revit shows the file is fixed, and the file cannot be rebuilt from it. The address itself, file names and file contents are never stored for this. A converted file reported as not opening in Revit moves from finished to failed. The totals are shown publicly on the home page.
Server logs
Server logs never contain file names or file content.
Deletion requests and questions
To have a report deleted early, email [email protected] or open an issue at GitHub issues with your report code. The code alone identifies nothing about you or your file.
Source code
The Revit Downgrade website and server are open source, so you can check exactly how your files are handled: github.com/PhanCongVuDuc/revit-downgrade. The conversion engine itself is closed source.
The code is public, so you can check these rules yourself:
Who makes Revit Downgrade
Revit Downgrade is made and run by one person, Phan Cong Vu Duc, an engineer from Vietnam. Each version step is tested by downgrading real project and family files and opening the results in the older Revit. Revit Downgrade is not affiliated with or endorsed by Autodesk.