Closing all open apps at once (iPad)

On IPad I want to control what apps are opened right now and often I want to close all apps that I'm not going to use just to clean up opened apps list and also free up resources. But I can't find a way to close all Apps at once, only one by one. Really Apple, why just not to add such a simpler feature that will make life easier for many people?

iPad Pro, iPadOS 17

Posted on Apr 2, 2024 9:50 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 3, 2024 3:00 AM

Unlike many other Operating Systems, the iPad system architecture is optimised for power efficiency and fast switching between Apps. While fully closing an open App may be helpful in some circumstances - such as your usage case for easy switching between a limited number of open Apps - doing so increases battery utilisation and reduces overall system performance.


By design, it should not be necessary to manually close any open Apps. iOS/iPadOS is designed to transparently and seamlessly manage its available resources as you switch between Apps and tasks. In force-closing "unloaded" Apps, you are simply clearing saved-state information that is used to rapidly restore an App to a running state.


Some understanding of how memory management works within iOS/iPadOS might help to clarify. To be clear, this is not intended to be an in-depth explanation, but will hopefully capture the essentials in basic terms...:


Your iPad/iPhone will always attempt to maximise use of its available RAM; unused RAM in this low power/high performance system architecture is essentially a wasted resource. 


iOS/iPadOS Apps are generally in one of four states - the first three are the most relevant.

  • The App is “Active” - it is running in the foreground. When you switch tasks, the App will continue to run in active state for some minutes before its resources are released and the App is placed into an Inactive state.
  • The App is “Inactive” but remains loaded in [fast] RAM. In this state, the App can be instantly restored to an Active state - but is not consuming CPU or other resources whilst in the inactive state.
  • The App is “Inactive” and unloaded. In this state, the App has been completely unloaded (releasing RAM for use by other processes) but its running state has been saved to [slow] flash memory. Returning to an App in this state will cause the App’s saved state to be reloaded from flash memory into Active RAM - without the need to re-initialise the App.
  • The App has been closed. All running data has been expelled - there is no “saved” state; relaunch will reload and re-initialise the App from scratch.


Memory management is generally a juggling act - and for the most part, you should allow the OS to manage its memory space. Re-initialising an App is the slowest and most power hungry method of launching an App. Inactive Apps do consume some system resources, but by design, the required system resources to maintain this state are insignificant.


Force-closing an App releases all resources and purges saved-state data. Whilst the mechanism exists to do so (and in rare circumstances manual intervention to terminate an App may be necessary), a force close generally reduces system performance.


All that said, there are instances where manually closing an App has merit - your described usage case being one of them. While closing Apps individually from the App Switcher page is quick, requiring just one upward swipe for each open App, it is clearly not as convenient as being able to simultaneously close all open Apps. Perhaps consider that having a facility to simultaneously close all Apps carries inherent risk of accidentally losing unsaved App-data...


Apple does invite submission of comments and feature requests via its Product Feedback portal. If you would like to see additional functions in a future release of iPadOS, this would be the most appropriate channel through which to make a request. For iPad and iPadOS:

Feedback - iPad - Apple


4 replies
Question marked as Top-ranking reply

Apr 3, 2024 3:00 AM in response to Vedmant

Unlike many other Operating Systems, the iPad system architecture is optimised for power efficiency and fast switching between Apps. While fully closing an open App may be helpful in some circumstances - such as your usage case for easy switching between a limited number of open Apps - doing so increases battery utilisation and reduces overall system performance.


By design, it should not be necessary to manually close any open Apps. iOS/iPadOS is designed to transparently and seamlessly manage its available resources as you switch between Apps and tasks. In force-closing "unloaded" Apps, you are simply clearing saved-state information that is used to rapidly restore an App to a running state.


Some understanding of how memory management works within iOS/iPadOS might help to clarify. To be clear, this is not intended to be an in-depth explanation, but will hopefully capture the essentials in basic terms...:


Your iPad/iPhone will always attempt to maximise use of its available RAM; unused RAM in this low power/high performance system architecture is essentially a wasted resource. 


iOS/iPadOS Apps are generally in one of four states - the first three are the most relevant.

  • The App is “Active” - it is running in the foreground. When you switch tasks, the App will continue to run in active state for some minutes before its resources are released and the App is placed into an Inactive state.
  • The App is “Inactive” but remains loaded in [fast] RAM. In this state, the App can be instantly restored to an Active state - but is not consuming CPU or other resources whilst in the inactive state.
  • The App is “Inactive” and unloaded. In this state, the App has been completely unloaded (releasing RAM for use by other processes) but its running state has been saved to [slow] flash memory. Returning to an App in this state will cause the App’s saved state to be reloaded from flash memory into Active RAM - without the need to re-initialise the App.
  • The App has been closed. All running data has been expelled - there is no “saved” state; relaunch will reload and re-initialise the App from scratch.


Memory management is generally a juggling act - and for the most part, you should allow the OS to manage its memory space. Re-initialising an App is the slowest and most power hungry method of launching an App. Inactive Apps do consume some system resources, but by design, the required system resources to maintain this state are insignificant.


Force-closing an App releases all resources and purges saved-state data. Whilst the mechanism exists to do so (and in rare circumstances manual intervention to terminate an App may be necessary), a force close generally reduces system performance.


All that said, there are instances where manually closing an App has merit - your described usage case being one of them. While closing Apps individually from the App Switcher page is quick, requiring just one upward swipe for each open App, it is clearly not as convenient as being able to simultaneously close all open Apps. Perhaps consider that having a facility to simultaneously close all Apps carries inherent risk of accidentally losing unsaved App-data...


Apple does invite submission of comments and feature requests via its Product Feedback portal. If you would like to see additional functions in a future release of iPadOS, this would be the most appropriate channel through which to make a request. For iPad and iPadOS:

Feedback - iPad - Apple


Apr 3, 2024 3:16 AM in response to LotusPilot

Thanks for full explanation, but performance-wise it's not necessarily true. Closing all apps prior to running a resource hungry game for example will improve performance of a game. Otherwise while game will gradually increase RAM demand, iOs firstly will start compressing RAM, which is CPU (and power) demanding task, then will start unloading background apps when some RAM pressure is reached (which also requires CPU). And by doing this background work it will decrease performance of currently running app. So by clearing all apps before running a game for example will increase it's performance, avoid lags and improve power efficiency as there will be no need for not needed RAM compression.


Apr 3, 2024 1:41 AM in response to Rudegar

The main point is not to optimize resources but to have a clean opened apps list when I switch between them, then when I finish some part and don’t need all of opened apps I want to close them all to switch to some different task. Now the only way is to do it one by one. Which is probable an apple way to say users just suffer instead of offering a good solution.


Also about resources, mo matter if someone want to prove that keeping all apps open is ok, that’s not ok, when you open resource hungry app it will start compressing memory and closing background apps one by one, and that WILL have performance impact of currently running app.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Closing all open apps at once (iPad)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.