# Optimizing Animated Corona Proxy File Size from GrowFX Trees

**URL:** <https://forums.chaos.com/t/optimizing-animated-corona-proxy-file-size-from-growfx-trees/159611>\
**Category:** Help Required\
**Created:** [April 30, 2025, 9:14am UTC](https://forums.chaos.com/t/optimizing-animated-corona-proxy-file-size-from-growfx-trees/159611 "2025-04-30T09:14:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hake998](https://avatars.discourse-cdn.com/v4/letter/h/f04885/32.png) [@hake998](https://forums.chaos.com/u/hake998)\
**Post date:** [April 30, 2025, 9:14am UTC](https://forums.chaos.com/t/optimizing-animated-corona-proxy-file-size-from-growfx-trees/159611/1 "2025-04-30T09:14:28Z")

</div>

Hello ;

I’ve noticed that after converting GrowFX tree files—especially to animated Corona Proxy formats—some individual files can reach sizes of up to 40 GB per tree. Additionally, the conversion process tends to utilize only about 15% of the total CPU resources, significantly slowing down the workflow.

Is there a way to reduce the file size during or after conversion? Also, is it possible to configure the system to leverage the full capacity of the CPU (or all processor threads/nodes) to speed up the conversion process?

Any advice or optimization tips would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![maru](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/maru/32/15975_2.png) [@maru](https://forums.chaos.com/u/maru)\
**Post date:** [May 12, 2025, 8:54am UTC](https://forums.chaos.com/t/optimizing-animated-corona-proxy-file-size-from-growfx-trees/159611/2 "2025-05-12T08:54:50Z")

</div>

Continuing in support ticket #376311.

---

<div class="post-metadata">

**Author:** ![maru](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/maru/32/15975_2.png) [@maru](https://forums.chaos.com/u/maru)\
**Post date:** [May 22, 2025, 2:44pm UTC](https://forums.chaos.com/t/optimizing-animated-corona-proxy-file-size-from-growfx-trees/159611/3 "2025-05-22T14:44:26Z")

</div>

As to models resulting in very large proxy files - some (limited) optimizations are possible, but we don’t yet have any timeframe that we could share.

As to low CPU usage when exporting proxies, this is internally logged for our team as (Report ID=CMAX-1646).