# Project with many screens makes slow thunkable

**URL:** <https://community.thunkable.com/t/project-with-many-screens-makes-slow-thunkable/2642982>\
**Category:** Feedback\
**Tags:** screen, thunkable-bugs\
**Created:** [October 13, 2023, 5:31pm UTC](https://community.thunkable.com/t/project-with-many-screens-makes-slow-thunkable/2642982 "2023-10-13T17:31:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [October 13, 2023, 6:49pm UTC](https://community.thunkable.com/t/project-with-many-screens-makes-slow-thunkable/2642982/4 "2023-10-13T18:49:25Z")

</div>

If you are displaying text or images on each screen, you would use a placeholder component.

For example, let’s say you have a different image on each screen. Instead of making 1,000 screens, you make one screen and you name the images image1.jpg, image2.jpg, image3.jpg, etc. You create a variable called PageNum and set it to 1.

Then you assign the image component’s picture a value joining “image” with PageNum and with “.jpg”. When the user clicks the next page button, you increase PageNum by one and re-load the image component. There is no need to have more than one screen.

---

_[View the full topic](https://community.thunkable.com/t/project-with-many-screens-makes-slow-thunkable/2642982)._