How to hide expressions in .aep file….

[Dan Ebberts]

You can use the ExtendScript Toolkit to create a .jsxbin binary file from the expression (File > Export as Binary…), then you can wrap the file’s contents in double quotes and drop it in an eval() expression. The resulting expression will look something like this:

eval(“@JSXBIN@ES@2.0@MyBbyBn……..”);

A word of caution though–my experience is that you can end up taking quite a performance hit doing this, especially if the expression is complex.

Dan

[Xavier Gomez]

Tricky!
I tried this on an expression designed for a text layer. And suprise:
Had to use double eval otherwise…… 🙂

Xavier.

[Luis Garcia]

Great! I will try, I think that is the thing I need…. Thanks!

[Yoan Boisjoli]

I know this thread is pretty old, but I ran into the same problem recently. Dan’s jsxbin approach still works, but the performance hit can be pretty rough on heavier expressions.

I needed something simpler for client deliveries, so I ended up building a small tool called Hugly. It doesn’t hide expressions completely, but it uglifies them enough that they’re not readable at a glance, and you can also beautify them again when you need the clean version. It keeps the comp running normally since it doesn’t rely on eval tricks or binary includes.

If you’re curious, here it is: https://aescripts.com/hugly

Might help someone else landing on this thread years later like I did.