Workflow: How to capture a memory snapshot

- Open the Memory Profiler.
- Decide which target to profile, e.g., the Editor itself or a running Player (either on your local machine or on a connected device).
- In the Memory Profiler window, click the Attach drop-down menu and select the target to profile.
- Click the Capture button at the top of the Memory Profiler. The snapshot will appear on the left side of the Memory Profiler window in the Workbench panel.
Note: The Capture button will be labeled Capture Editor when the Memory Profiler is targeting the Editor, and the Editor is not in Play Mode. In that case, it will capture the Editor. If the target is a built Player or the Editor in Play Mode, it will be labeled Capture Player. Capturing a snapshot of the Editor while in Play Mode will include any memory used by the Editor as well. Memory usage in a Play Mode player is not representative of the memory usage on a device. It is always recommended to capture snapshots from a built Player on the targeted platform.
You can also trigger a memory snapshot at any moment you decide, without any interaction with the Memory Profiler window. Use the Memory Profiler Scripting API to set up capture logic in a script inside your Player. For information about custom MetaData collection, see Add Player hook.
Back to manual
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.