Overview#
Fusion is cloud-first. Your designs live in Autodesk's cloud, versioned automatically, which is a huge advantage over a single drive that can fail. But cloud-first is not the same as "backed up under your control". Accounts get suspended, subscriptions lapse, people delete the wrong folder, a bad sync overwrites good data, and engineers need to work on planes and in shops with no network. This page covers three linked topics: how offline mode works, how to back up your data to storage you control, and how to export in formats that outlive any single product.
Note: Offline behaviour and export formats are taken from Autodesk's current help. Items marked "not confirmed" are general guidance, not Autodesk data.
Where to find it#
- Offline mode: the Job Status icon at the top right of the Application bar; its flyout has the Working Online / Working Offline toggle. A red dot on the icon means offline; a yellow dot means detected latency.
- Cache a design, folder or project: right-click it in the Data Panel and choose Add to Offline Cache (projects: Cache This Project, or the Data Panel Settings icon). Settings > View Offline Cache greys out items that are not cached.
- Cache time: avatar > Preferences > General > Offline cache time period (days).
- Recovery after a crash: File > Recover Documents.
- Export: File > Export; the web client can download files and folders (folders are zipped).
- Archive of a project: the web client folder download; a project can also be archived (see the hubs page), which is not a backup.
How offline mode works#
| Aspect | Documented behaviour |
|---|---|
| Entering offline | Manual toggle in Job Status, or automatic for scheduled service maintenance (announced by in-product banner 72 hours ahead), an unexpected outage, or no internet connection. Fusion returns online automatically when the condition clears |
| Time limit | Offline mode is available for two weeks at a time, then you must reconnect and sign in to validate the license |
| Available files | Designs, folders and projects you cached manually, plus files you opened (downloaded and cached automatically) |
| Cache freshness | Cached designs are not auto-synced with newer versions; re-cache to refresh. Items stay cached for the number of days you set |
| Allowed offline | Edit cached designs; Insert Component, Insert Derive and Derive with cached components |
| Not available offline | Uploading files, creating folders, creating milestones/versions, and viewing design history (except Fusion for education) |
| Saving | Saves update the Data Panel and are queued; the queue is not subject to the cache time limit. Last-save-wins: only the most recent saved changes sync |
| Referenced designs | You cannot pick a particular change of a referenced design; when you go online the last saved state is uploaded |
| Interrupted uploads | If you lose connection or close Fusion mid-upload, the upload continues when you reconnect |
Note: not confirmed in Autodesk's documentation: a dedicated conflict dialog when a teammate also saved the same file. The documented rule is last-save-wins, so coordinate before editing shared files offline.
Preparing to go offline#
- While online, right-click the designs, folders or projects you need and choose Add to Offline Cache; check progress in Job Status. Include referenced components.
- Set Offline cache time period (days) long enough for the trip.
- Check the grey-out view (View Offline Cache) to confirm everything you need is cached.
- Remember the two-week limit and plan a sign-in before it ends.
- Optionally export a local
.f3dor.f3zcopy of critical designs as a safety net.
Working offline#
- Save often; saves queue for upload.
- Do not plan to create versions or milestones, upload files or view history offline.
- Cloud-based tasks such as rendering and simulation need a connection (general expectation; the latency note only says caching is unavailable when latency is detected).
Coming back online#
- Toggle back to Working Online (or let Fusion do it) and watch Job Status until uploads finish.
- Re-cache anything you still need offline, and Get Latest on references.
- Check the History dialog for your saves.
Warning: Do not clear the cache or uninstall Fusion while offline saves are pending (general caution).
Crash recovery#
Recovery documents are cached locally. After an unexpected close, use File > Recover Documents, select the file and Open, then Save; Fusion saves it as the latest version. You can also Delete recovery files from the cache.
Desktop Connector offline#
Desktop Connector has a separate Work Offline mode (see the Autodesk Docs page). Fusion design files are cloud-only in the connector, so use Fusion's own cache for them.
Why back up when it is in the cloud?#
| Risk | Example | Backup that helps |
|---|---|---|
| Human error | Folder deleted, wrong state saved as latest | Trash restore; periodic exports (no purge period is documented) |
| Account problems | Subscription lapse, suspended or compromised account | Local archives readable without a subscription |
| Product change | Format or feature retirement | Neutral-format exports (STEP) |
| Cloud outage | Service unavailable at a deadline | Local copies |
| Staff departure | Personal hub files vanish | Project-level backups |
| Compliance | Records retention mandates | Immutable archives |
| Ransomware/malicious deletion | Compromised admin deletes data | Offline or off-site copies |
The mirrored Fusion help does not describe Autodesk's redundancy or recovery promises; check the current terms and your plan. What the help does say: after a license term expires you keep Basic Access (view projects and files including history, comment, download if permitted), and a deleted project is permanently deleted, with previously shared links no longer working.
Backup methods#
Method 1: manual export of key milestones#
For each release milestone, export:
- The native .f3d (single design) or .f3z archive (design with external references; a design with external references cannot be exported as .f3d, only as other formats including .f3z).
- A STEP file for neutral geometry.
- PDF drawings.
- A BOM (CSV or spreadsheet).
- A text file listing versions, milestones and approvals.
Store the set in your own storage (NAS, cloud drive of your choice, archive tape), named by revision and date. Keep at least two copies on separate media.
Method 2: project download#
The Fusion web client lets you download files and folders; folders are zipped and include .f3d and .f3z archive files. Fusion design files are not included in a folder download and must be downloaded one at a time, because a format must be chosen. Run a full project download on a schedule (monthly for active projects) and keep several generations.
Method 3: scripted backup with Autodesk Platform Services#
For teams with many projects, use the Data Management API to enumerate the hub, project and folder tree, then download the latest (and milestone) versions of every item to a backup server. Outline:
- Register an application in the Autodesk Platform Services portal to get a client ID and secret.
- Authorise with an OAuth token for a user who has access to the hub (general; check what Autodesk currently supports for your hub type).
- Call hubs, projects, folders and items endpoints; for each item list versions and obtain download URLs.
- Save files into a dated directory structure and write a manifest (item, version, milestone, hash).
- Run on a schedule (Task Scheduler, cron) and alert on failure.
- Test a restore every quarter.
Note: not confirmed in Autodesk's Fusion documentation: Autodesk Platform Services Data Management API for hub backups. This is an advanced developer option and a reasonable investment only once the data is business-critical.
Method 4: Fusion's local scripts and add-ins#
Fusion's own API (Python or C++, documented in the API reference) can export the open design. An add-in can iterate over documents and export each one; it is slower than server-side downloads. Check your licence terms for automation (not covered in the help).
Export formats and longevity#
Formats the Fusion export command lists: Fusion (.f3d, .f3z), 3MF, Inventor (.ipt, .iam), DWG, DXF, FBX, IGES, LMV (.svf), OBJ, SAT, SketchUp (.skp), SMT, SPD, STEP and STL, USDZ. An exported design does not stay associative with the original.
| Format | Preserves | Loses | Longevity (general guidance) |
|---|---|---|---|
| F3D / F3Z | The Fusion design (F3Z with references) | Needs Fusion to open | Depends on Autodesk |
| STEP | B-rep geometry, assembly structure | History, parameters | Very high |
| IGES | Surfaces/solids | Many details | Declining |
| SAT/SMT | ACIS-family solids | History | Medium |
| STL/3MF/OBJ | Mesh | Exactness, features | High but lossy |
| DXF/DWG | 2D | The 3D model | High |
| PDF drawings | 2D | The 3D model | Very high (drawing outputs have their own help topic) |
Rule: archive both. The native format keeps editability; STEP and PDF keep long-term readability.
Retention policy#
Write a short retention policy:
- What is backed up: all active projects, plus libraries.
- How often: daily for APIs, weekly for downloads, per-milestone for exports.
- How many generations: for example 7 daily, 4 weekly, 12 monthly, indefinite per release.
- Where: two separate locations, one off-site.
- Who: a named owner and a deputy.
- Test: restore a random project every quarter.
For regulated products, retention requirements (often 10 to 30 years or product life plus years) apply to released data. Neutral formats and PDFs are the safest long-term bets.
Disaster recovery scenarios#
| Scenario | Recovery |
|---|---|
| Deleted a file today | Restore from the project's Trash folder in the web client (Editor or higher; folder admins can Delete forever); otherwise restore from backup |
| Saved a bad state | Open the earlier entry from History and use File > Save As Latest |
| Account locked | Contact Autodesk support; use local backups meanwhile |
| Subscription ended | You keep Basic Access (view, comment, download if permitted); export models in Fusion. Export before the term ends |
| Cloud outage | Fusion switches to offline mode automatically; work on cached files (up to two weeks) |
| Corrupt design | Open an earlier entry from History; try the exported F3D; as a last resort import the STEP |
Options reference#
| Option | What it does | Notes/default |
|---|---|---|
| Working Online / Offline toggle | Switches offline mode | Job Status flyout; two weeks at a time |
| Add to Offline Cache / Cache This Project | Stores items for offline use | Not auto-updated; re-cache |
| Offline cache time period (days) | How long cached items stay cached | Preferences > General |
| Recover Documents | Reopens crash recovery files | File menu; Save makes it the latest |
| Export F3D/F3Z | Native backup | F3Z for references |
| Export STEP | Neutral backup | No history |
| Folder download (web) | Zipped folder download | Design files individually |
| Move to Trash / Restore / Delete forever | Delete and recover | Editor+; Delete forever is folder admin |
| Save As Latest | Makes an older state the newest | See the versions page |
Tips and pitfalls#
Tip: Automate the backup. Manual backups that depend on goodwill stop happening in busy weeks.
Tip: Name exported files
<number>_<rev>_<yyyymmdd>.<ext>so the archive sorts itself.
Warning: A backup you never restored is a hope, not a backup. Test.
Warning: Exported F3Z files can be large and contain referenced data. Store them with the same access control as the originals.
Warning: Offline mode lasts two weeks at a time. Do not plan a month-long remote trip without testing a full offline cycle first.
Practice exercise#
Pick an assembly with three components. Do the full cycle: (1) open all components to cache them; (2) add them to the offline cache, switch to Working Offline and make an edit and save; (3) reconnect and confirm the change appears in History; (4) export an F3Z, a STEP and a PDF of the assembly into a dated folder with a manifest text file; (5) open the F3Z in a fresh session to prove it restores. Expected result: a tested archive set and a note of your cache time setting and the two-week offline limit.
Related#
- Versions, Milestones and Lifecycle States (this section)
- Sharing and Public Links (this section)
- Admin Console and Team Best Practices (this section)
- Getting started: Versioning and Milestones