Green Tips, by Department

The section is visualized in our One Studio, Many Actions Infographic.

The producer has more influence over a production's carbon footprint than any other role—not by doing green tasks, but by shaping how the production is planned and managed. The highest-leverage decisions happen during pre-production, before compute-intensive work begins.

• Design for fewer revisions. Every unnecessary asset, revision cycle, and re-render has an energy cost. Build realistic review milestones and revision limits into schedules, briefs, and contracts.
• Plan for asset reuse. Develop reusable asset libraries, naming conventions, and file management systems from the outset to reduce duplicate work across future productions.
• Choose sustainable technical partners. Ask render farms, cloud providers, and key vendors about their renewable energy sourcing, energy efficiency, and environmental commitments when selecting suppliers.
• Schedule compute strategically. Work with Pipeline leads to schedule rendering and simulation workloads efficiently and, where possible, on lower-carbon infrastructure.
• Measure your footprint. Use the P4P Animation Carbon Calculator to establish a baseline and identify opportunities for improvement throughout production.

Operational decisions shape a studio's ongoing environmental impact, regardless of the projects underway.

• Improve office energy efficiency. Use LED lighting, automated equipment shutdowns, and ENERGY STAR® certified equipment to reduce everyday energy consumption.
• Support sustainable hybrid work. The CMPA case study found home heating to be the largest emissions source for one Vancouver animation studio. Help remote staff reduce home office energy use by sharing information on energy efficiency, rebates, and power management.
• Reduce business travel. Prioritize virtual collaboration where appropriate. When travel is necessary, favour direct flights, economy class, and lower-emission transportation options.
• Manage waste responsibly. Provide clearly labelled recycling, organics, landfill, battery, and e-waste collection, and ensure electronics are recycled through certified programs.
• Purchase sustainably. Consider environmental criteria when buying office equipment, catering, furniture, and supplies, including recycled content, local sourcing, durability, and minimal packaging.

Many of the biggest opportunities require collaboration across creative, technical, and production teams rather than action by any one department.

• Standardize workflows. Consistent pipelines, naming conventions, and asset management reduce rework, troubleshooting, and unnecessary compute across productions.‍
• Build sustainability into team culture. Include sustainability in onboarding, production planning, and professional development so every department understands how its decisions affect the production's footprint. Ontario Green Screen, Reel Green, and Producing for the Planet all offer free tools and training.‍
• Track progress over time. Monitoring emissions across productions helps studios identify trends, set targets, and demonstrate progress to funders, broadcasters, and partners.‍
• Watch for the rebound effect. Faster rendering and more efficient tools only reduce emissions if they result in less work overall—not simply more iterations or larger workloads. Track total compute alongside efficiency gains to ensure improvements translate into real reductions.

Story and editorial decisions made early in production have compounding effects downstream. A shot that gets cut in previs costs nothing to render. The same shot cut after the final render costs everything.

• Invest in previs. Thorough previsualization reduces the number of surprises that generate costly late-stage revisions. Proxy media and low-resolution stand-ins allow creative decisions to be made without triggering full-quality render cycles.‍
• Practice disciplined version control. Unnecessary versions of sequences, cuts, and assets accumulate storage costs and create confusion that generates re-work. Establish clear naming conventions and version management protocols from day one.‍
• Use proxy media aggressively. Working with full-resolution assets for editorial decisions that don't require them wastes storage and compute. Establish clear protocols for when full-resolution assets are actually needed.‍
• Catch problems early. A story problem identified at script stage costs a conversation. The same problem identified at composite costs weeks of rework across multiple departments. Editorial should be actively involved in identifying potential rework risk as early as possible.

Asset creation choices made in the art department ripple through every subsequent stage of production. The lightest asset that achieves the creative result is always the right asset.

• Right-size texture resolution. Texture maps larger than the production output resolution waste memory and increase render times without improving visible quality. Establish clear texture resolution standards at the start of production and enforce them consistently.‍
• Build reusable asset libraries. Assets designed for reuse — with consistent naming, clean topology, and modular construction — reduce duplication across episodes and productions. Invest the time upfront; it pays back across every subsequent production that draws from the library.‍
• Control AI asset generation. AI tools for texture and asset generation can accelerate production — and can also generate enormous quantities of unused or duplicate assets. Set clear production norms for AI-generated asset use: what gets generated, by whom, and what gets kept.‍
• Use compression deliberately. Appropriate compression of textures and assets reduces storage and data transfer demands significantly. Establish compression standards that balance quality requirements against file size.

Geometry complexity and rig design are among the most direct technical determinants of render time and energy use. The modeler and rigger who think about downstream efficiency are doing sustainability work, whether or not they frame it that way.

• Reduce polygon counts intentionally. Use the minimum geometry that achieves the required visual quality at the required output resolution. Establish LOD (Level of Detail) standards that match polygon density to actual production needs.‍
• Use instancing instead of duplication. Instanced geometry consumes a fraction of the memory and render resources of duplicated geometry. Establish this as a default workflow practice rather than an afterthought.‍
• Design lightweight rigs. Complex rigs with unnecessary controls slow simulation and playback across the pipeline. Rigs should be designed for the performance required — not for every possible performance.
• Reuse and share rigs across characters and productions. Modular rig components that can be shared across characters reduce both build time and the compute associated with re-rigging similar character types.
• Layout efficiency matters. Scene assembly choices — how assets are organized, referenced, and loaded — directly affect playback performance and render times. Layout artists should be briefed on efficiency standards at the start of production.

Animation is inherently iterative — but not all iteration is necessary. The difference between creative iteration that serves the work and technical iteration generated by unclear briefs or inadequate previs is significant, and it shows up in compute hours.

• Clarify briefs before animating. Unclear direction generates rework. Animators who receive clear, specific direction from directors and supervisors before they begin produce better work with fewer revisions. This is both a quality argument and an efficiency argument.‍
• Use real-time engines for blocking and approval. Real-time preview tools allow creative decisions to be made and approved at a fraction of the compute cost of full-render review cycles. Establish a production protocol where major creative approvals happen at the lowest appropriate resolution.‍
• Cache selectively and manage cache storage. Simulation and dynamics caches accumulate rapidly and consume significant storage. Establish clear protocols for which caches get kept, for how long, and where — and audit storage regularly.‍
• Watch the AI rebound. AI motion tools can accelerate blocking and secondary animation significantly. They can also generate enormous quantities of variations that never get used. Set production norms for AI animation use that capture the efficiency gains without multiplying total compute.

Lighting and rendering sit at the intersection of creative quality and computational intensity. The lighting TD and render wrangler who understand sustainability are among the most valuable people on a green production.

• Use AI denoising. AI-based denoising allows high-quality renders to be produced with significantly fewer samples, reducing render times substantially. This is one of the clearest cases where AI adoption directly reduces emissions without triggering rebound — the creative result is equivalent, the compute is lower.‍
• Optimize lighting setups before final render. Complex lighting with unnecessary lights, excessive bounces, or unoptimized sampling settings multiplies render time without proportional quality gain. Lighting review should include a technical efficiency check before shots go to final render.‍
• Minimize test render quality. Full-quality test renders are one of the most common sources of wasted compute in production. Establish clear render quality tiers — low-res for blocking approval, medium for lighting review, full-quality only for final output — and enforce them consistently.‍
• Manage the render farm actively. Idle render nodes, inefficient job queuing, and poor load balancing waste significant compute. Render wranglers should be empowered to optimize farm utilization, not just submit jobs.
• ‍Choose render infrastructure based on grid emissions. Where your render jobs run determines a significant portion of their carbon footprint. Prioritize render farms and cloud regions in low-carbon grid locations — BC, Quebec, and Ontario within Canada; renewable-powered regions for cloud infrastructure. Ask your render farm provider for their energy sourcing information.

FX and simulation are among the most compute-intensive stages in a 3D pipeline, and also among the most prone to unnecessary recomputation when upstream changes aren't managed carefully.

• Cache simulations aggressively. Recomputing simulations that have already been approved is one of the most wasteful sources of compute in production. Establish clear cache management protocols — what gets cached, at what stage, and what triggers a required recompute versus what can be managed with existing cache.‍
• Reduce simulation resolution where possible. Not every simulation needs to run at full resolution. Establish resolution standards that match simulation quality to actual output requirements — hero elements at full resolution, background elements at reduced resolution where the difference is not visible.‍
• Plan simulation dependencies carefully. Simulations that depend on upstream elements are vulnerable to late-stage changes that require full recomputation. Identify simulation dependencies early and protect them in the production schedule.‍
• Avoid unnecessary complexity. The most realistic fluid or crowd simulation that the shot actually needs is the right simulation. Complexity beyond what is visible at output resolution wastes compute without improving the work.

Compositing is generally less compute-intensive than rendering and simulation, but it sits at the end of the pipeline where the accumulated costs of upstream inefficiency become visible and expensive.

• Optimize node structures. Compositing trees that are unnecessarily complex — with redundant operations, inefficient branching, or unoptimized processing order — slow render times without improving output quality. Regular node tree reviews are worth the investment.‍
• Manage file formats and codecs deliberately. The choice of intermediate file formats significantly affects both storage requirements and processing time. Establish clear standards for which formats are used at which stages of the pipeline.‍
• Coordinate with upstream departments early. The most expensive compositing work is rework caused by upstream changes — a lighting revision, a new render pass, a changed asset. Compositing supervisors should be involved in production planning conversations, not just at the point of delivery.‍
• Audit render passes. Productions regularly render passes that are never used in final composite. A pre-production audit of required render passes — and a regular review during production — can significantly reduce wasted compute.

Pipeline and IT sit across the entire production — their decisions affect every other role's environmental footprint, often invisibly. This is a role with significant sustainability leverage that is rarely framed that way.

• Implement tiered storage. Not all data needs to live on high-performance, energy-intensive storage. Active project data belongs on fast storage; completed project data belongs on archival storage; obsolete data should be deleted. Establish and enforce a data lifecycle policy.‍
• Delete unused assets and duplicates. Studios accumulate enormous quantities of redundant data — duplicate assets, unused renders, outdated versions. Regular storage audits and clear deletion policies can significantly reduce storage-related emissions.‍
• Power down idle machines. Workstations and render nodes left running overnight and on weekends consume significant energy for no productive output. Remote device management tools — like NinjaOne, used by Kickstart Studios — allow IT teams to power down and wake devices remotely without disrupting workflows.‍
• Right-size hardware procurement. Studios frequently overprovision high-performance machines for roles that don't require them. Match hardware specifications to actual role requirements — reserve high-performance machines for rendering and simulation, use lower-power devices for administrative and lighter creative work.‍
• Track performance per watt. When evaluating hardware, measure output per watt rather than raw performance. A machine that renders faster but draws significantly more power may have a worse performance-per-watt profile than a more modest alternative.‍
• Extend hardware lifecycles. The embodied carbon in manufacturing a new workstation is significant. Extend hardware life through RAM and SSD upgrades, regular maintenance, and reassignment of older machines to lower-intensity roles rather than replacement.
• ‍Certify e-waste recycling. Partner with certified e-waste recyclers — R2 or e-Stewards certified — for end-of-life hardware disposal. Uncertified recycling or landfill disposal of electronic equipment releases hazardous materials and loses valuable recoverable materials.

The render farm — whether on-premise, cloud-based, or hybrid — represents the largest concentration of energy use in an animation pipeline. The decisions made about render infrastructure have more environmental impact than almost any other technical choice in the studio.

• Choose infrastructure based on grid emissions. BC and Quebec offer some of the cleanest electricity in North America for on-premise or locally hosted render infrastructure. For cloud rendering, major providers — AWS, Azure, Google Cloud — operate data centres in Canadian regions powered by clean hydro. Match your compute location to the cleanest available grid.‍
• Ask render farm providers for their energy sourcing. Commercial render farms vary significantly in their sustainability commitments and energy sourcing transparency. Make this part of your vendor selection criteria. Some farms offer carbon-neutral or renewable-powered options — understand what those claims actually mean before relying on them.‍
• Enable autoscaling. Cloud render infrastructure that scales to demand — spinning up nodes when needed and releasing them when not — avoids the energy waste of idle capacity. Work with your cloud provider to implement autoscaling rather than maintaining a fixed, always-on node count.
• Schedule jobs for lower-carbon periods. Electricity grid carbon intensity varies by time of day and season. Tools like Electricity Maps allow studios to schedule non-urgent render jobs during periods of lower grid emissions — overnight when renewable generation is proportionally higher, for example.
• Minimize data transfer. Transferring large files between storage locations and render infrastructure consumes energy in networks and data centres. Minimize unnecessary data movement through efficient pipeline architecture, local caching, and proximity of storage to compute.
• Ask about cooling technology. Cooling accounts for nearly 40% of total data centre energy consumption, making it one of the highest-impact efficiency variables in render infrastructure. Immersion cooling — where servers are submerged in non-conductive liquid rather than cooled by air — reduces data centre energy consumption by approximately 50% compared to conventional air cooling, according to peer-reviewed research published in Energy Informatics. When evaluating render farm providers, ask what cooling technology they use. It is a meaningful differentiator.‍
• Monitor and report render farm emissions. The render farm's energy use should be tracked and reported as part of the production's carbon footprint. Work with your render farm provider to obtain energy consumption data, and apply the appropriate regional grid emissions factor to calculate your rendering footprint.