Great question—this inconsistency often boils down to the core purposes, underlying technologies, and target audiences behind each Autodesk cloud service. Let’s break it down:

1. Target Audience & Use Case Priorities #

• A360 is built as a user-friendly collaborative hub for everyday Fusion 360 users, hobbyists, and small teams. Its export options are tailored to common, hands-on workflows: sending designs to CNC machines (DXF), moving work to Inventor for advanced CAD tasks, or importing into SketchUp for architectural visualization. It prioritizes simplicity and immediate usability for non-technical folks.
• Forge ModelDerivative is an enterprise-focused API platform for developers building custom, automated applications. Its format support leans into industry-standard, machine-readable formats (like STEP, IGES, OBJ, glTF) that fit seamlessly into scalable pipelines. Formats like DXF, Inventor, or SketchUp are either less critical for enterprise automation, require Fusion-specific logic, or have licensing constraints that make them a lower priority for a general-purpose developer tool.

2. Underlying Export Technologies #

• A360’s export tool directly uses the same core engine as the desktop Fusion 360 app. When you export from A360, it’s essentially running the exact export logic you’d use locally—so it supports every format Fusion natively handles, including those tied to other Autodesk products (Inventor) or popular consumer tools (SketchUp).
• Forge ModelDerivative relies on a separate, cloud-optimized processing pipeline designed to handle a wide range of CAD formats from multiple Autodesk products (AutoCAD, Revit, etc.) consistently. Adding Fusion-specific exports like Inventor or SketchUp would require integrating specialized Fusion export logic into this pipeline, which adds significant complexity and doesn’t align with Forge’s broader goal of universal CAD processing.

3. Licensing & Ecosystem Constraints #

• Some formats (like Inventor) are tightly linked to Autodesk’s product-specific licensing and ecosystem. A360’s deep integration with Fusion 360 lets it leverage existing licensing agreements to enable exports to other Autodesk tools. Forge, as a third-party developer platform, has to balance accessibility with licensing restrictions—making it harder to include format exports tied closely to specific Autodesk product workflows.
• SketchUp’s format has its own technical nuances and licensing considerations. While Fusion can export to it directly, adding this support to Forge would require additional partnerships or technical work that hasn’t been prioritized yet.

In short, each service’s format support reflects its unique mission: A360 is for end-users to collaborate and move designs between tools easily, while Forge is for developers to build scalable, automated CAD processing workflows.

内容的提问来源于stack exchange，提问作者MHilgers