# Does the MakeCode compiler leave constants in Flash memory to save RAM?

**URL:** <https://forum.makecode.com/t/does-the-makecode-compiler-leave-constants-in-flash-memory-to-save-ram/1103>\
**Category:** Arcade\
**Created:** [January 22, 2020, 10:50pm UTC](https://forum.makecode.com/t/does-the-makecode-compiler-leave-constants-in-flash-memory-to-save-ram/1103 "2020-01-22T22:50:28Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kjw](https://avatars.discourse-cdn.com/v4/letter/k/e79b87/32.png) [@kjw](https://forum.makecode.com/u/kjw)\
**Post date:** [February 5, 2020, 6:27pm UTC](https://forum.makecode.com/t/does-the-makecode-compiler-leave-constants-in-flash-memory-to-save-ram/1103/5 "2020-02-05T18:27:52Z")

</div>

What would the technique described in [Best practice making levels with the new tilemap editor](https://forum.makecode.com/t/best-practice-making-levels-with-the-new-tilemap-editor/1133) do with the levels in the array, would they end up in RAM?

I’ve been using a big `if` statement for level switching which that OP describes as inelegant but maybe I’ve minimised the amount of RAM usage (by luck)?

---

_[View the full topic](https://forum.makecode.com/t/does-the-makecode-compiler-leave-constants-in-flash-memory-to-save-ram/1103)._