Overview#
Fusion performance depends on three things: your computer (especially the graphics card, memory, and single-core CPU speed), the settings that control how the canvas is drawn, and the structure of your design. A slow session is almost always caused by one of these, and you can usually improve it without buying anything. This page works from the cheapest fixes (settings and habits) to the most expensive (hardware).
Fusion is a hybrid application. Much of the modeling kernel runs locally and is mostly single-threaded, so a fast CPU core helps with feature recomputes. The cloud affects saving, opening, and anything that depends on the network (cloud render, simulation solves, data sync). Rendering in-canvas uses the local CPU and GPU. Distinguishing local from cloud causes tells you where to look.
Note: The hardware figures in the table below (RAM sizes, core counts, SSD advice) are general industry guidance, not Autodesk data; the help mirror does not publish system requirements. Check Autodesk's current system requirements page before buying hardware. The graphics settings sections are checked against the Preferences reference.
Where to find it#
- Graphics and display settings: Preferences (Application bar > My Profile > Preferences) > Graphics, plus Display Settings on the Navigation Bar (graphics presets are available there too).
- Graphics presets: Performance, Quality and Custom. Performance optimizes graphical performance but may reduce visual quality. Changing Canvas Effects overwrites Custom.
- Graphics Diagnostic: Help > Support and Diagnostics > Graphics Diagnostic shows GPU Device, GPU RAM, GPU Driver API, and (Windows only) driver version, date, a check for driver updates and a Use Software Renderer option, plus the status of High Resolution Graphics, Anti Aliasing, Ambient Occlusion, Object Shadow, Ground Shadow, Ground Reflection, Selection Display Style and Transparency Effect.
- Report Performance Issue: Help > Support and Diagnostics > Report Performance Issue records OS data during a slow workflow (10 minute limit) and sends it to the Fusion performance team.
- Task manager or Activity Monitor: your operating system's tool to see whether CPU, GPU, memory, or network is the bottleneck.
- Graphics card control panels: NVIDIA Control Panel, AMD Software, or Intel Graphics Command Center, used to pick the high-performance GPU for Fusion.
- Timeline and browser: where design structure problems show themselves.
Hardware: what actually matters#
| Component | Why it matters | Guidance |
|---|---|---|
| Graphics card (GPU) | Draws the canvas; critical for orbiting large assemblies and rendering | A dedicated GPU with current drivers; integrated graphics work for small parts but struggle on large assemblies |
| CPU single-core speed | Feature recompute is largely single-threaded | A modern CPU with high boost clocks beats many slow cores for modeling |
| CPU core count | Helps rendering, simulation preprocessing, mesh operations, and CAM | More cores matter for local render and toolpath calculation |
| RAM | Large assemblies and meshes consume memory | General guidance only: more RAM helps large assemblies and meshes; check official minimums |
| Storage | Cache and temp files; opening designs | An SSD is strongly recommended; a nearly full drive slows everything |
| Network | Opening, saving, sync, cloud tools | Wired or strong Wi-Fi; latency matters more than raw bandwidth |
| Display | Many pixels cost GPU time | Very high resolution on integrated graphics hurts; consider reducing scaling |
| Mouse | Three-button mouse is faster than a trackpad | A real middle button is more important than DPI |
Laptops#
Laptops with both integrated and dedicated graphics sometimes run Fusion on the integrated GPU. Open the operating system's graphics settings and set Fusion to use the high-performance GPU. On battery, many laptops throttle; keep the power plugged in and set the power plan to high performance when modeling or rendering.
Operating system notes#
- Windows: keep graphics drivers current but avoid beta drivers. If a recent driver update introduced crashes, roll back to the previous version.
- macOS: the September 3, 2026 release notes say Metal is now the default graphics driver on macOS. Keep macOS within the versions Fusion supports (check Autodesk's requirements).
- Virtual machines and remote desktops: GPU acceleration is often missing or limited, which can cause display glitches and slow performance. Support is not confirmed in Autodesk's documentation.
Graphics and display settings#
Heavy visual effects cost frames per second on weaker graphics hardware. The following settings can be adjusted from Display Settings in the Navigation Bar and from Preferences.
| Setting | Effect on performance | Notes |
|---|---|---|
| Graphics preset: Performance | Optimizes performance, may reduce visual quality | Quality does the opposite |
| Dynamic | Automatically reduces or switches off graphics settings in priority order to hold the minimum frame rate | Set the Minimum framerate during navigation (FPS) |
| Ground Plane | Enables ground shadows and reflections | Turn off when not needed |
| Ground Shadow / Ground Reflection | Shadows and reflections on the ground plane | Off while modeling |
| Object Shadow | Bodies cast shadows on other bodies | Off while modeling |
| Ambient Occlusion | Shading based on exposure to ambient light | Off while modeling |
| Anti-Aliasing | Smooths curved edges and surfaces | Reduce on slow GPUs |
| Transparency Effect | Advanced Transparency looks better but could degrade performance | Use the simpler setting |
| High-resolution canvas graphics | Scales graphics on high-DPI displays; disabling may improve performance | No effect at 100% DPI scaling |
| Animate view transitions | Animates named view and sketch view transitions; uncheck to improve performance | |
| Environment Dome | Virtual sky and horizon effect | Canvas Effect |
| Use Software Renderer (Windows) | In Graphics Diagnostic | For diagnosis, not speed |
| Object visibility | Hidden bodies are not drawn | General guidance: hide what you are not editing |
Tip: Create two saved habits: model in plain Shaded with effects off, then turn effects on only when preparing a screenshot or a render.
Working with large designs#
The biggest performance gains come from structure, not hardware.
Reduce what is drawn#
- Hide, don't just ignore. Turn off the visibility (lightbulb) of components you are not working on. Hidden objects are not drawn, which helps orbiting.
- Isolate. The marking menu context menu includes Isolate/Unisolate.
- Use simplified stand-ins for fasteners and purchased parts (general guidance).
- Avoid modeled threads except where you must print or export them (general guidance).
- Delete or hide construction clutter. Many origin planes, sketches, and construction axes add overhead. Hide them from the browser.
Reduce what is calculated#
- Keep the timeline lean. Hundreds of small features slow recompute when you edit early features. Combine operations where it makes sense and delete features that no longer contribute.
- Avoid heavy patterns of complex features. A rectangular pattern of a fillet-covered boss with a thread 500 times is expensive. For feature patterns, Compute Type (available when Object Type is Features) offers Optimized (identical copies by patterning feature faces; fastest), Identical (replicates the original features' results; use when Optimized is not possible) and Adjust (potentially different copies, each instance calculated individually; slowest).
- Group features in the timeline to keep it readable; grouping itself does not speed up compute, but it helps you find expensive items.
- Be careful with massive fillets, shells, and lofts on complex bodies. These can take seconds to minutes to compute and may fail near tolerance limits.
- Convert and simplify imports. A STEP file of a full vendor assembly may contain thousands of tiny faces. Use only the envelope you need, or find a simplified model.
- Turn off auto-compute for sketches where fixed constraints keep things simple (not a toggle; the idea is to avoid heavy equation-driven sketches).
Meshes#
Dense STL or OBJ meshes (hundreds of thousands to millions of triangles) are heavy. Reduce or remesh before further operations (see the mesh pages in section 07; the Mesh release notes mention an Edge Length remeshing method). Avoid converting very dense meshes to B-Rep without reducing first.
Assemblies#
For large assemblies, see the dedicated large assemblies page in section 05. Key practices include breaking the assembly into sub-assemblies stored as separate designs linked as external references, keeping joints simple, and using rigid groups and grounding to reduce solver load.
| Practice | Benefit |
|---|---|
| Split the product into several designs | Each file opens quickly; you open only what you need |
| Use Insert into Current Design with external references carefully | Updates flow but loading cost remains |
| Break links when a component is finished | Stops update checks |
| Use fewer joints | Fewer constraints to solve |
| Avoid contact sets unless you need collisions | Collision detection is expensive |
Cloud and network performance#
- Saving is slow: large files take time to upload. Save less often if you must but not rarely; the real fix is to split designs.
- Opening is slow: the first open downloads data; later opens use the local cache. See the cache page in this section.
- Sync stalls: check your network, then the service status page of Autodesk. Corporate proxies and firewalls can interfere.
- Offline work: offline mode is available for two weeks at a time, then you must reconnect and log in (Job Status icon > Working Online toggle).
Step by step: a one-hour tune-up#
- Close other heavy programs and browser tabs. Check available memory and storage.
- Update graphics drivers from the manufacturer (not through a generic updater) and restart.
- Force Fusion to use the dedicated GPU in the operating system's graphics settings.
- Open Display Settings and select the Performance preset, or turn off shadows, reflections, ambient occlusion and anti-aliasing.
- Reduce Windows display scaling or resolution temporarily to see if the GPU is the limit.
- Open a slow design. Hide all components except one and test orbit speed.
- In the timeline, locate the slowest features by editing early items and noticing delays. Simplify or delete these.
- Replace modeled threads and heavy standard parts with simpler stand-ins.
- Use Service Utility > Reset if opening is erratic (see the crashes page). Autodesk says clearing cached data can reduce long startups caused by a bloated cache.
- Re-test. If still slow, check the task manager for the real bottleneck.
Options reference#
| Option | What it does | Notes/default |
|---|---|---|
| Display Settings > graphics presets | Performance / Quality / Custom | Performance for large designs |
| Canvas Effects | Shadows, reflections, ambient occlusion, anti-aliasing | Off for modeling |
| Graphics presets | Performance, Quality, Custom | Preferences > Graphics, Display Settings |
| Isolate / Hide | Reduces what is drawn | Use freely |
| Cosmetic thread | Shows a thread without modeling it | Default in Hole |
| Compute Type (patterns) | Optimized (fastest), Identical, Adjust (slowest) | Only when Object Type is Features |
Tips and pitfalls#
Tip: If orbiting is smooth but edits are slow, the bottleneck is feature compute (CPU and design structure). If edits are fast but orbiting stutters, the bottleneck is graphics.
Warning: Do not run more than a few large designs open at once. Each open tab holds the whole design in memory.
Warning: Disabling effects does not change the final render; it only changes what you see while modeling. If a screenshot looks flat, turn effects back on.
Tip: Keep 15 to 20 percent of your drive free. A nearly full SSD slows writes and temp files.
Tip: For rendering, use cloud render or schedule local renders for after hours (see the rendering section) instead of tying up your machine.
Practice exercise#
- Open your largest design. Note orbit smoothness on a scale of 1 to 5.
- Turn off shadows, reflections, and anti-aliasing. Note the change.
- Hide all components except the one you are editing. Note the change.
- Edit a dimension in an early timeline feature and time how long the recompute takes. Repeat after deleting one unused feature.
- Record which change gave the biggest improvement.
Expected result: you know whether your bottleneck is graphics, CPU, memory, or design structure, and you have at least one permanent habit change.
Related#
- Crashes, bugs, and cache clearing (this section)
- Large assemblies (Components and Assemblies)
- Preferences (Getting Started)
- The timeline (Parametric Design)