Kindle frozen? Hold the power button for a full forty seconds

1. The forty-second hold, done properly

Amazon's procedure is precise and the duration is the whole point. Press and hold the power button until either a power dialog box appears or the screen goes blank. Then continue holding for 40 seconds and release. After a few seconds, the charge indicator light turns back on and the device reboots.

The failure mode is releasing early. A Kindle's screen going blank part-way through feels like the reset has happened, so people let go — and a blank e-ink screen is exactly what a frozen, powered-down or flat device also looks like. Nothing distinguishes them visually, which is why the instruction is a count rather than a cue. Time it rather than estimating.

Amazon also notes what to do if the device does not come back by itself: press or slide the power button to restart it. That is a normal outcome rather than a failure — the long hold cuts power, and some models then need a short press to boot rather than starting on their own. If you have done the forty seconds and nothing happens, try one ordinary press before concluding the reboot failed.

The screen going blank is not the finish line. It is roughly the halfway point of the hold, and letting go there is the single most common reason this documented procedure appears not to work.

2. When the hold does nothing, charge before retrying

If the forty-second hold produces no response at all, Amazon's next step is power rather than another reset: plug the device in using the USB cord or power adapter that came with it, let it charge for 30 minutes, then unplug it and try to restart again. A Kindle with a fully depleted battery cannot boot, and it cannot tell you that either, because an e-ink screen needs power to change what it displays.

Amazon does give one clear signal for this state: a battery symbol with an exclamation mark means the battery has zero charge left and needs charging. If you see that, stop resetting and start charging — no button combination will help a device with no power in it.

Use the cable and adapter that came with the Kindle, or ones you have confirmed work. A Kindle draws very little current, so it will happily charge from almost anything — which cuts both ways, because a marginal cable can supply just enough to light the indicator and not enough to bring a flat battery back. If thirty minutes on one cable produces nothing, try a different cable and a mains adapter rather than a computer port before deciding the device is dead.

3. When it freezes again, find the trigger

A Kindle that reboots successfully and then freezes again has a cause rather than a fault, and it is usually findable. The most common one is a specific book — a large PDF, a sideloaded file with unusual fonts, or a title that failed partway through downloading. If the device freezes reliably when you open one item, that item is the problem and removing it resolves the symptom.

The pattern to watch for is where it freezes. Locking up on the home screen, on a particular book, or while syncing each point somewhere different: the library index, a single file, or the network layer. Note which it is before doing anything drastic, because it changes what is worth trying.

Storage pressure and pending updates both contribute. A Kindle nearly full has little room to work with, and a device that has been offline for a long time may be trying to apply a queued software update every time it wakes. Connecting to Wi-Fi and leaving it plugged in for an hour lets a pending update finish, which resolves a category of recurring freeze that no amount of rebooting will.

Deregistering or factory resetting a Kindle removes downloaded content and settings. Try removing a suspect book first — purchased content stays in your library and can be downloaded again, so deleting one title from the device costs nothing.

4. Slow rather than frozen

Sluggishness and freezing are the same family and Amazon documents them together, but they warrant different patience. E-ink refreshes slowly by design — a page turn is not instant on any Kindle, and full-screen refreshes that flash black are normal behaviour rather than a fault. Judge slowness against how the device behaved a month ago, not against a phone.

Genuine slowdown usually traces to the library rather than the reader. A very large collection, a lot of sideloaded files, or many items with rich covers all make the home screen work harder. If the reading experience is fine and only the library is slow, that is the cause and reducing what is stored on the device helps directly.

The same forty-second reboot is the right first response to slowness. It clears whatever has accumulated in memory, and it is the step Amazon points to for both symptoms. If it improves things for a day and then degrades again, that pattern points at storage or a specific item rather than at a device that needs replacing.

5. Frozen, off, or flat — telling them apart

This is the confusion e-ink creates, and it is worth stating plainly: a Kindle displaying a book page is not necessarily on. E-ink holds its last image indefinitely without power, so a device that ran out of battery mid-book keeps showing that book for weeks. People conclude the device is frozen on a page when it is simply switched off and empty.

The charge indicator light is the honest signal here, because it needs power to work. Plug the Kindle in and look for it. A light that comes on means power is reaching the device and the battery is taking it. No light at all after several minutes on a known-good cable and mains adapter points at the cable, the port, or the device — and a charging port full of pocket lint is worth checking with a torch before assuming worse.

Give a deeply discharged Kindle real time. Thirty minutes is Amazon's figure before retrying the restart, and a device that has been flat for months may need longer before it responds at all. The combination that indicates a genuine hardware problem is specific: no charge light, on two cables and a mains adapter, after an hour, with a clean port.

6. Resets, and what to tell support

There is an order to the more drastic options and it is worth respecting. The forty-second reboot loses nothing. Removing a suspect book loses nothing meaningful, since purchased content re-downloads. A factory reset erases downloaded content, settings and registration, and should be the last thing you try rather than an early one — particularly if the device holds sideloaded files that exist nowhere else.

Back up anything irreplaceable before a reset. Purchased Kindle books live in your Amazon account and come back; personal documents and sideloaded EPUBs or PDFs may not, unless they were sent through Amazon's own document service. Connecting the Kindle to a computer by USB and copying the documents folder takes a couple of minutes and is worth doing first.

When you contact Amazon, give them the observations rather than the symptom. Say whether the forty-second hold produced any response, whether the charge indicator light comes on when plugged in, whether you left it charging thirty minutes before retrying, whether it freezes on a specific book or on the home screen, and whether a battery symbol with an exclamation mark appeared. Those five answers separate a flat battery from a corrupted item from a device that needs replacing.

Frequently asked questions

Sources and review notes

Checked on September 7, 2026. Compiled by Glitchary from Amazon’s Kindle support documentation. Button positions differ slightly between Kindle generations, and Fire tablets follow separate procedures despite sharing some help pages — check Amazon’s article for your device. Amazon blocks automated access to its help pages, so these citations were verified by URL and Amazon-authored title with content read through search restricted to amazon.com rather than fetched directly; check the pages by hand before relying on a specific step. Glitchary is independent of Amazon.

• Amazon: how to reboot your Kindle e-reader
• Amazon: slow or frozen Kindle e-reader or Fire tablet
• Amazon: Kindle e-reader support and troubleshooting guide