Not Enough Memory to Open This Page: Safe Fixes

Written by Amir Iqbal · Reviewed by Umar Abbas · August 30, 2026

You tap a link, the page starts to load, and then, instead of the article or shop you wanted, you see the message not enough memory to open this page. It feels like your phone or computer is broken, or like the website has failed, but in most cases neither is true. The message means your browser ran out of working memory at that moment, so it could not finish building the page. Working memory, often called RAM, which stands for random access memory, is short term space your device uses for things that are open right now: tabs, apps, images, and videos. When that space fills up, the browser stops the heaviest page to protect the rest of the device, and it shows this message instead.

The good news is that this problem is usually fixable in a few minutes, with safe steps that do not risk your files or accounts. You do not need to change system settings, install a cleaner app, or delete important data. You need to free working memory, give the browser a clean start, and, if the page is very heavy, open it in a lighter way. This guide walks through those steps in order, from the quickest fix to the deeper checks, for browsers on computers and for browsers on phones. It also explains why one page fails while other pages work, when clearing cache helps and when it only signs you out, and which habits stop the message coming back every week.

Work through the steps in order, and test the page after each step, because the first step often fixes it, and there is no need to do every step if the page already opens. Save any unsaved work first, such as a form you are filling in or a document you are editing in another tab, because closing tabs and restarting a browser will lose unsaved typing in those tabs. If the page is a shopping checkout or a form with payment details, do not rush: note the order or form details first, or finish that task on a device with more free memory, rather than forcing a struggling browser to handle a payment. Our guide on practical steps for deep work makes a similar point about closing extra tabs: fewer open tabs means more attention for you, and more memory for the browser.

What Working Memory Is, and Why It Runs Out

Think of your device as a desk. Storage, which is the long term space for files, photos, and apps, is like a filing cabinet: large, slow to search, and able to hold a lot. Working memory is like the desk surface itself: smaller, fast, and only for the papers you are using right now. A browser puts each open tab, each image, each video, and each interactive part of a page onto that desk surface. A light news article takes a small corner of the desk. A page with many high resolution images, autoplay videos, maps, chats, and ads can spread across the whole desk at once. When the desk is full, the browser cannot lay out the next page, so it stops and shows the memory message.

That desk fills up faster than people expect, because browsers and phones keep more open than you see. A tab you opened yesterday and forgot about still uses memory. A video paused in another tab still holds memory. Apps running in the background on a phone, such as maps, music, chat, and email, also use working memory, even when you are not looking at them. Add a heavy page on top of that full desk, and the browser has nowhere to put it. This is why the same page may open fine in the morning, when few tabs are open, and fail in the evening, when twenty tabs and several apps are running. The page did not get heavier. Your desk got fuller.

First Fix: Close Tabs You Do Not Need

Start with the simplest fix, because it frees the most memory with the least risk. Look at your open tabs and close every tab you do not need for the page you are trying to open. On a computer, close tabs one by one with the small cross on each tab, or right click a tab and choose the option to close other tabs if your browser offers it, but only after you have saved anything important in those tabs. On a phone, open the tab view, which usually shows tabs as cards, and swipe away or tap the cross on each card you no longer need. Keep only the tab for the page you want, plus any tab with unsaved work you must finish first.

Pay special attention to heavy tabs, because not all tabs use the same amount of memory. Tabs with videos, maps, online documents, social feeds, and shopping sites usually use far more memory than plain text pages. A paused video tab, a map tab zoomed into a busy city, and a social feed that keeps loading new posts are three of the heaviest kinds of tabs, and closing just those three can free more memory than closing ten light text tabs. If you need a tab later, bookmark it, which saves its address in a list you can reopen, instead of keeping it open all day. Bookmarking is free, instant, and it turns a memory hog into a one click reopen later.

After you close tabs, wait a few seconds, then reload the failed page with the reload button or the F5 key on a computer keyboard. Do not open the page in a new tab on top of the old failed tab, because that keeps the old tab's memory in use as well. Close the failed tab itself, open a fresh tab, and type or paste the address again, or use your bookmark. If the page opens now, you have found your answer: the browser was simply full. Typing the address in a fresh tab, as search google or type a url advises for sensitive pages, also avoids following a stale link. Make a habit of closing tabs at the end of each work session, and your browser will stay faster and more stable, not just for this page, but for every page after it.

Second Fix: Restart the Browser, Then the Device

If closing tabs does not fix the page, restart the browser completely. Closing the browser window is not always a full restart, because some browsers keep running in the background, or reopen the same tabs at once. On a computer, close all browser windows, check that the browser icon no longer shows it as running, and then open the browser again with only one tab. On a phone, swipe the browser away from the recent apps view, which is the list of apps you recently used, and then reopen it. That clean start clears temporary memory build up, stops background pages, and gives the failed page a fresh, empty desk to load onto.

If a browser restart still does not fix the page, restart the device itself, which is a stronger clean start. On a computer, use the restart option in the start or Apple menu, not just sleep or closing the lid, because sleep keeps working memory as it is. On a phone, hold the power button and choose restart, or power off, wait ten seconds, and power on again. A restart closes every app, clears working memory completely, and lets the device start fresh, which fixes a wide range of temporary memory problems. Save your work first, because a restart closes unsaved documents, and give the device a minute after restart before you open the heavy page, so startup apps can settle. After a restart, a phone may ask for its startup password, and enter password to unlock 30 30 attempts remaining explains that counter for the legitimate owner.

Update the Browser, and Check Extensions

An out of date browser can use memory badly, because newer versions fix memory leaks, which is a plain term for a bug where a program keeps holding memory it no longer needs, and slowly fills the desk until pages fail. Check for a browser update in the browser's own menu, usually under Help or About, and install it if one is offered, then restart the browser again. Updates also fix security problems, so keeping a browser up to date is good practice even when memory is not the issue. If you use more than one browser, test the failed page in a different browser with one tab open, because a page that opens in one browser but fails in another points to a problem in the first browser, not to the page or the device.

Extensions deserve a check too, because a faulty or heavy extension can eat memory on every page you open. An extension is a small add on, such as an ad blocker, a coupon tool, a password tool, or a screen recorder, that runs inside the browser. Try opening the failed page in a private or incognito window, which is a browser window that usually runs without most extensions and without saved site data, and see whether the page opens there. If it opens in private mode, an extension is likely part of the problem. Go back to a normal window, turn extensions off one by one, starting with the ones you installed most recently or use least, and test the page after each change, so you find the culprit instead of turning everything off at once.

Clear Cache Carefully, With a Warning About Sign Outs

Clearing cache is a useful step, but it needs a warning first, because it is easy to clear too much. Cache is a store of saved images, files, and page parts that the browser keeps so pages load faster next time. Clearing cached images and files is safe: it does not delete your files, photos, or bookmarks, and it does not delete saved passwords on its own. It does mean pages may load a little slower the next time, while the browser saves those parts again. That small cost is worth it when a corrupted or oversized cache is part of a memory problem, because a fresh cache gives the browser a clean set of page parts to work with.

The warning is about the other boxes on the same screen. Many browsers offer to clear cookies and site data on the same screen as cache, and clearing those will sign you out of websites, so you will need to sign in again, with passwords and, where you use it, two step codes. Cookies, as Safari's cookie guidance explains, are small files websites store to remember you, such as keeping you signed in. If you clear cookies by accident, you have not lost your accounts, but you will face a round of sign ins, and any site where you forgot the password will become a recovery task. So, when you clear data, tick only cached images and files, read every ticked box before you confirm, and leave cookies, passwords, and history unticked unless you have a specific reason to clear them and you know your passwords.

To clear cache, open the browser settings, find the privacy or clear browsing data section, choose a time range such as the last hour or all time, tick only cached images and files, and confirm. Then close and reopen the browser, and test the failed page with one tab open. On a phone, the same setting lives in the browser app settings, not in the phone's general settings, so open the browser first. If the page opens, the cache was part of the problem. If it does not, you have still done no harm, because you cleared only cache, and you can move on to the phone specific checks next. For a broader view of keeping a device safe while you change settings, our guide on simple steps that keep malware off a computer explains why official settings beat third party cleaner tools.

On a Phone: Close Apps and Free Storage Space

Phones feel memory errors more than computers, because phones have less working memory and because many apps run in the background. Open the recent apps view and swipe away apps you are not using, especially maps, video apps, games, and social apps, which hold large amounts of memory even when paused. Then test the page again in the browser with one tab open. If the page opens, background apps were the cause, and a habit of closing heavy apps before opening a heavy page will prevent most repeats. You do not need to close every app every time, but closing the heaviest ones before a demanding page is a quick, effective habit.

Storage space matters too, even though it is different from working memory. When a phone's storage is nearly full, the device has little room to swap temporary data, which is a technique where the device moves less used data to storage to free working memory, and the whole phone slows down. Check storage in the phone settings, and if it is nearly full, free space by deleting large videos you have backed up, removing apps you no longer use, and clearing downloads you no longer need. Do not delete photos or messages in a panic: back them up first, check the backup, and only then delete the local copy. Freeing even a few gigabytes of storage can make a struggling phone feel noticeably faster, and it gives the browser more room to work.

Also check whether your phone has a software update waiting, because updates often improve memory handling, and a phone that has not been updated in a long time may be running an old browser engine. Update over Wi-Fi, with the phone charged, and restart after the update. If the phone is very old and the page is very heavy, accept a lighter way to read the page, such as a reader view, which is a browser mode that shows text and main images without ads and extra page parts, or a text version of the page if the site offers one. Reader view is found in the browser address bar or menu on most phones, and it can turn an unopenable page into a readable one in seconds, without any risky change.

When One Page Fails but Others Work

A page that fails while other pages open is telling you something useful: the problem is likely that page's weight, not your device as a whole. Heavy pages combine many large images, embedded videos that start loading at once, interactive maps, comment sections, and advertising parts that each use memory. On a device that is already busy, that combination can cross the memory limit, while a plain text page stays well under it. Test this theory by opening the failed page on a different device or a different browser, with one tab open, and by opening a light page on the original device. If the heavy page fails everywhere, the page itself is unusually heavy, and lighter reading options are the right answer.

For a heavy page, try reader view first, as described above, because it strips the heaviest parts and keeps the main text and images. Try a different browser, because browsers handle heavy pages differently, and a page that fails in one browser may open in another. Try opening the page on a computer instead of a phone, if you have one, because computers usually have more working memory. Try again at a quieter time, with only the browser open, no video playing, and no downloads running, because a download or a video in another tab can be the extra weight that tips a heavy page over the limit. None of these steps changes the page or your device settings, and together they cover most single page failures.

Habits That Stop the Message Coming Back

Stopping this message long term is about habits, not about buying tools. Keep open tabs to a small number, such as under ten on a phone and under twenty on a computer, and bookmark pages to read later instead of keeping them open. Restart the browser at least once a day if you browse heavily, and restart the phone or computer at least once a week, so temporary memory build up never grows into a failure. Keep the browser updated, keep extensions to the ones you actually use, and remove the rest. These four habits cost minutes a week and prevent most memory errors, in the same way that tidying a desk each evening prevents a morning where nothing fits on it.

For phones, add two more habits: close heavy apps after use, rather than leaving games, maps, and video apps running all day, and keep at least a few gigabytes of storage free, so the device always has room to manage temporary data. For computers, add one more habit: close programs you are not using before you open a heavy web app, such as a large document, a design tool, or a video editor in the browser, because those web apps need a large share of working memory to themselves. If you regularly work with heavy web apps, consider whether your device's memory is enough for that work, and plan an upgrade when you can, but do not treat an upgrade as the first fix: habits and restarts fix most cases for free.

Finally, know what not to do. Do not change advanced browser settings, such as memory flags or experimental options, unless you understand them and can reverse them, because a wrong change can make the browser unstable. Do not install cleaner, booster, or RAM freeing apps, because they often close apps aggressively, which makes the device reload them and use more memory, not less. Do not delete system files, and do not factory reset a phone or computer for a single page error, because a reset erases data and settings for a problem that a tab close or a restart usually fixes. Safe, reversible steps first, in order, is the rule that protects both your data and your time.

Conclusion

Not enough memory to open this page usually means the browser ran out of working memory at that moment, not that your device is broken or the website is gone. Close tabs you do not need, restart the browser, and restart the device, testing the page after each step, because those safe steps fix most cases. Update the browser, test in a private window to find a bad extension, and clear only cached images and files, remembering that clearing cookies will sign you out of websites. On a phone, close background apps, free storage space, and try reader view for a very heavy page. Keep tabs few, restart regularly, and keep the browser updated, and the message should become rare. If a page still fails after all safe steps, with one tab open on a restarted device, note what you tried and contact the site owner or device support with those details, because a clear record helps them find a deeper cause faster.

Frequently Asked Questions

Relevant blogs

Back to all blog guides · Back to Tips and Tricks guides