Here’s a tight, big-picture summary of Fusion 360—this is the mental model you want to keep in your head while working.
The core building blocks
Components
- Represent real parts
- Own sketches, bodies, and features
- Are the primary unit of reuse
- Assemblies are just components that contain other components
Sketches
- Define 2D intent
- Always belong to one component
- Are either:
- Part sketches (inside components), or
- Layout sketches (at the root / assembly)
Parameters
- Live at the document (assembly) level
- Are global and reusable
- Control dimensions everywhere
- Must be named intentionally to avoid collisions
Sketch state matters
Sketch open
- You define geometry and constraints
- No 3D operations allowed
Sketch closed
- You create features, joints, and assemblies
- History becomes stable
Sketches aren’t always open because Fusion separates definition from execution.
Hierarchy & references
- Sketches inherit hierarchy from their owning component
- Root sketches do not move with components
- Component sketches do move with components
Safe referencing
- Root → component
- Within same component
- Component → component
(use Project or parameters) - Avoid sketch-to-sketch coupling without intent
Reuse rules (remember these)
- Reuse components , not sketches
- Assemblies are reused by inserting designs
- Parameters are reusable, but:
- prefix them
- keep shared ones minimal
One-paragraph takeaway
Fusion 360 is built around components as parts, sketches as intent, and parameters as logic. Assemblies are just organized components, sketches are owned and scoped, and parameters are global but disciplined. If you activate the right component, sketch locally, reference upward intentionally, and reuse components instead of geometry, your designs stay stable—even as they grow.
I