Overview
Maya is the animation and effects package that most feature and episodic pipelines are still built around. Character work is the core of it: a skeleton and deformation system that scales to production rigs, skinning with corrective shapes, constraints and drivers, and a graph editor that gives an animator direct control over every curve and tangent in the scene.
The simulation side is a full package in itself. Cloth, hair and fur, rigid and soft bodies, and the fluid and particle solver for smoke, fire and liquid, all cached to disk so a shot can be simulated once and played back at speed. Motion graphics style procedural node work sits alongside it for effects that are generated rather than hand animated.
Pipeline integration is why studios keep it. USD is native, so scenes assemble from layered stages rather than one monolithic file, references and proxies keep heavy assets out of the working scene, and the entire application is exposed to scripting so a studio can build its own tools on top. The bundled renderer handles look development in the viewport with progressive refinement.
What it does well
Rigging and animation
Production scale skeletons, skinning with correctives, constraints, drivers and a graph editor with full tangent control and layered animation.
Simulation solvers
Cloth, hair, fur, rigid and soft bodies, plus the fluid and particle solver for smoke, fire and liquid, all disk cached for playback.
USD pipeline
Native stage loading, layering and variant handling so scenes assemble from shared departments instead of one large file.
Procedural node graph
Effects and motion graphics built from nodes rather than keyframes, with instancing driven by fields and expressions.
Scripting layer
The whole application is scriptable, which is why studio tooling and plug-in ecosystems settle around it.
Changes in this build
- USD stage handling extended with faster layer muting and variant switching on heavy scenes.
- Viewport playback improved for scenes with many deformed characters.
- New retopology and symmetry tools in the modelling toolkit.
- Cached playback now covers more deformer types without falling back to evaluation.
- Bundled renderer updated with faster progressive refinement in the viewport.
What is in the package
- Maya 2027 offline installer, 64-bit
- Bundled renderer with material and light libraries
- Simulation solver set
- USD plug-in and pipeline tools
- Multilingual interface packs, 6 languages
System requirements
| Processor | Intel or AMD 64-bit with SSE 4.2, 8 cores or more recommended |
| Memory | 16 GB minimum, 64 GB for simulation work |
| Graphics | Certified GPU with 8 GB VRAM recommended |
| Storage | 25 GB free plus cache space for simulations |
| Display | 1920 x 1080 minimum, three button mouse required |
| System | Windows 10 or Windows 11, 64-bit only |
Installation
- Extract the archive to a local drive with plenty of free space.
- Remove any partially installed Autodesk components before starting.
- Run setup and let the shared components install first.
- Set the project and cache directories on a fast drive at first launch.
- Open a sample scene once so the viewport shaders compile.
Before you start
Autodesk shared components are used by several applications, do not remove them while another is installed.
Simulation caches grow quickly, put them on a drive you are willing to fill.
Turn off the update service so the build stays aligned with any studio plug-ins.
Questions about this title
Is a renderer included?
Yes, the bundled renderer installs with the application and handles look development in the viewport.
Does it support USD?
Yes, USD stages load, layer and export natively.
Can it run beside another Autodesk application?
Yes, they share components and install into their own versioned folders.
Do older scenes open?
Yes, scenes from earlier cycles open and are saved forward.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.