# IL Post Processing **URL:** https://discussions.unity.com/t/il-post-processing/910090 **Category:** Post-Processing **Tags:** Scripting, Question **Created:** [February 22, 2023, 10:58pm UTC](https://discussions.unity.com/t/il-post-processing/910090 "2023-02-22T22:58:37Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![xoofx](https://dub1.discourse-cdn.com/unity/user_avatar/discussions.unity.com/xoofx/32/98105_2.png) [@xoofx](https://discussions.unity.com/u/xoofx) #### Post date: [February 23, 2023, 11:19am UTC](https://discussions.unity.com/t/il-post-processing/910090/2 "2023-02-23T11:19:52Z")
Hello peturdarri, > [@peturdarri](#): > > I have been using the undocumented IL post processing API in Unity in my projects for a few years now. It’s been an incredibly useful tool. Agreed, it can be very useful for scenarios that don’t work with Source Generators. 🙂 > [@peturdarri](#): > > Are there any plans to make this API public and officially supported? It is a good question. IL post processing (ILPP as we call it internally) was initially required internally for DOTS projects. It has helped to solve some problems but it has caused (and it is still to some extend) also significant performance regression during compilation time so that DOTS projects had to move a large part of their processing from ILPP to Roslyn Source Generators. As we will migrate from our custom compilation pipeline to MSBuild, it might make this custom process less relevant, as, for example, you will be able to use easily projects like [Fody](https://github.com/Fody/Fody) to perform IL transforms. That being said, we know that ILPP is not going away anytime soon, so we should revisit if we want to make this official. For sure, from what you are saying, we need to be very careful at not breaking it if many external projects are heavily relying on it! --- _[View the full topic](https://discussions.unity.com/t/il-post-processing/910090)._