We’ve been showing early versions of the new Memory Profiler throughout the year at Unite Berlin and Unite LA and... The public version is finally available! For the last months we’ve been busy getting the backend stabilized and improving the workflows in the UI. That said, this tool is only useful, if it helps you understand your project’s memory usage and solves actual problems you’re having with regard to memory. We know we’re not entirely there yet and have some ideas on how we can improve it but your feedback would help us greatly in informing our priorities, discovering new ideas and finding bugs or issues. Getting started: Download Unity 2018.30f2 or newer through the hub Open your project in Unity and go to Window > Package Manager Open the “Advanced” drop-down and make sure “Show Preview Packages” is set Select the Memory Profiler in the list of packages and click install. To get started, we recommend that you checkout the Documentation, and/or watch the presentations linked above. The presentation from Unite LA is still largely relevant, even if the UI might look slightly different. Unite Berlin 2018 Unite LA 2018 Feedback: In terms of feedback, we're especially looking for: Can you think of any usecases that are not covered yet? Are there any workflows that are unclear or missing? Is there anything that is unclear or that you don’t understand? Are there any issues or unclear parts in the documentation? Please feel free to post any feedback in this sub-forum. How to report bugs Ideally we'd like any bugs reported through the built in bug reporter tool, as that will automatically provide us with some relevant context. When reporting bugs, please: Attach a (stripped) project when there are issues with capturing snapshots. Attach snapshot files when there are issues with opening them. Profiling in the Editor As with all of Unitys Profiling tools, profiling results when profiling the playmode in the Editor are not something you should base your assumptions on. Always profile a built player on your target platform. Note: In case you've checked before and couldn't find it: The package is now visible in the Package Manager Window!