iPhone Camera Not Working? Fixes in Order (Black Screen, Blur, Permissions)

A black viewfinder, a blurry photo, and a camera app that refuses to open are three different faults that happen to share one app icon. Treating them as one problem leads to the wrong fix, usually a full reset for something a setting or a blocked lens could have solved. This guide shows how to fix iPhone camera not working by matching the symptom you actually see to the step that addresses it, starting with the checks that take seconds and cost nothing.

Start by describing the fault in one sentence. Does the camera open at all, does it open but show black, or does it take photos that never look sharp. That single sentence decides whether you are dealing with permission, hardware, or focus, and it saves you from working through a long list of steps that were never relevant to your phone.

What Usually Causes This

Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix iPhone camera not working starts with that match, because the right first step depends on the symptom in front of you.

Likely causeSign you will seeFirst check
Camera app frozenBlack screen or frozen previewForce close the Camera app and reopen it
Lens blocked or dirtyBlurry or hazy photosRemove the case and clean the lens
App permission offCamera fails in one app onlyCheck Settings, Privacy and Security, Camera
Screen Time restrictionCamera app missing or blockedCheck Screen Time, Content and Privacy Restrictions
Low storageCamera will not save photosFree space in Settings, General, iPhone Storage
Hardware damageOne camera black after a dropBook a service check after software steps fail

Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.

Before You Open the Camera App

Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.

When you approach fix iPhone camera not working, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.

Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.

iPhone camera visual tied to the Before You Open the Camera App section of this guide
iPhone camera visual tied to the Before You Open the Camera App section of this guide

How to fix iPhone camera not working in the Right Order

Working through fix iPhone camera not working in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.

  1. **Close the Camera app fully.** Swipe up from the bottom of the screen, or double press the Home button on older models, and swipe the Camera app away. Also close any other app that uses the camera, because a stuck camera session in one app can block the camera in every other app. Reopen Camera and test a photo. If the preview returns, the fault was a stuck app session. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  2. **Remove the case and clean the lens.** Take off the case and any lens protector, then wipe the rear and front lenses with a soft dry cloth. A thick or magnetic case can block a sensor or press on the lens area, and a smudged lens turns every photo soft. Test again without the case. If sharpness returns, refit the case carefully and check that no part of it covers the lens. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  3. **Switch between the front and rear cameras.** Tap the switch icon in Camera and test both cameras, then test video as well as photos. If one camera works and the other stays black, the fault is far more likely to sit in hardware than in settings. Note which camera fails, because that detail decides whether further software steps are worth your time. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  4. **Test the camera in another app.** Open FaceTime or another camera app and check whether the same fault appears there. A fault in one app only points at that app and its permission, while a fault in every app points at the system or the camera module. This single test saves you from resetting settings for an app level problem. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  5. **Restart the iPhone.** Power the phone fully off, wait about thirty seconds, and power it on again. A restart clears temporary camera service errors and releases a camera session held by a crashed app. Test Camera as soon as the phone restarts, before opening other apps, so a fresh app cannot seize the camera first. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  6. **Check camera permission for the affected app.** Open Settings, Privacy and Security, Camera, and confirm the app in question is allowed. A permission denied during setup leaves the app able to open without ever receiving an image. Toggle the permission off and on again, fully close the app, and reopen it to force a fresh permission check. At this stage of fix iPhone camera not working, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  7. **Check Screen Time restrictions.** Open Settings, Screen Time, Content and Privacy Restrictions, and confirm Camera is allowed. Restrictions set for a child, a shared device, or a managed profile can hide the Camera app entirely or block it without an error message. If restrictions are managed by someone else, ask them to review the Camera setting before going further. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  8. **Free up storage space.** Open Settings, General, iPhone Storage, and free space if the phone is nearly full. A camera that cannot save will sometimes refuse to open, and burst photos and video need working room. Remove large unused apps or old videos, then test Camera again. Keep a comfortable margin rather than freeing a single photo worth of space. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  9. **Update iOS.** Open Settings, General, Software Update, and install any available update. Camera faults that appear shortly after a major update are often fixed quietly in a following point release. Connect to Wi-Fi and power while updating, and test Camera after the phone restarts, since an interrupted update can leave the fault exactly where it was. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  10. **Disable VoiceOver and other overlays for a test.** Open Settings, Accessibility, and temporarily turn off VoiceOver and AssistiveTouch, then test Camera. Accessibility overlays can interfere with camera preview rendering after an update or a restore. If Camera works with them off, turn them back on one at a time to find which one conflicts. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  11. **Reset all settings.** Open Settings, General, Transfer or Reset iPhone, Reset, and choose Reset All Settings. This keeps your photos and files but returns settings such as Wi-Fi passwords and permissions to defaults, so note anything you will need to re-enter. Test Camera before restoring custom settings, so a restored setting cannot silently reintroduce the fault. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
  12. **Back up, then restore as a last resort.** Back up the phone, then restore it through a computer and test Camera before restoring your backup. A restore that fixes the fault points at deep software corruption, while a fault that survives a clean restore points at hardware. Do not skip the backup, because this step can erase content that has no other copy. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
iPhone camera visual tied to the How to fix iPhone camera not working in the Right Order section of this guide
iPhone camera visual tied to the How to fix iPhone camera not working in the Right Order section of this guide

Details People Often Miss

Camera faults feel dramatic because the symptom is visual, yet most of them have dull causes. A black screen usually means the camera service never started, a blurry image usually means the lens or the focus system cannot do its job, and a fault in one app usually means permission rather than hardware. Separating those three pictures at the start keeps the repair short, because each picture leads to a different group of steps. This distinction shapes how you should approach fix iPhone camera not working.

Focus behaviour deserves its own test. Tap different parts of the scene and watch whether focus locks, drifts, or never settles. A lens that focuses at one distance but not another, or a camera that hunts endlessly in good light, suggests a focus mechanism or stabiliser problem rather than a dirty lens. Clean the lens first anyway, since a smudge mimics a focus fault perfectly, and only then treat the focus system as the suspect.

Storage and heat also affect the camera more than most people expect. A phone that is nearly full may refuse to save, and a phone that is hot from gaming or long video recording may limit camera features to protect itself. Let a hot phone cool before judging a camera test, and free storage before concluding that the camera module has failed, since both conditions clear without any repair.

The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.

  • Close the Camera app fully
  • Remove the case and clean the lens
  • Switch between the front and rear cameras
  • Test the camera in another app
  • Restart the iPhone

Apple publishes iPhone camera and permission guidance through its official support pages, and the Settings paths in this guide follow those pages. See Apple Support for the current camera troubleshooting steps for your iOS version.

Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.

A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.

Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.

If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.

Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.

Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.

When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.

iPhone camera visual tied to the Details People Often Miss section of this guide
iPhone camera visual tied to the Details People Often Miss section of this guide

Mistakes That Make It Worse

The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.

  • Restarting the phone before closing the camera app, which wastes the simplest test on a fault that a force close would have fixed.
  • Replacing the phone or booking a repair before testing both cameras and a second app, which leaves the diagnosis unproven.
  • Cleaning the lens with a rough cloth or a household cleaner, which can scratch coatings that no setting can restore.
  • Resetting all settings as an early step, which erases Wi-Fi passwords and preferences for a fault that may sit in one app.
  • Ignoring a swollen battery, a cracked lens, or liquid damage and continuing to force the camera, which risks further damage.

Avoiding those errors keeps fix iPhone camera not working short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.

iPhone camera visual tied to the Mistakes That Make It Worse section of this guide
iPhone camera visual tied to the Mistakes That Make It Worse section of this guide

When to Stop and Get Help

Book a service check when one camera stays black across every app after a restart and an update, when the lens rattles or will not focus after cleaning, or when the fault began after a drop or liquid exposure. Take your notes on which camera fails and which steps you tried, because a service technician can move faster with that record than with a description of the symptom alone. Stop immediately if the battery looks swollen or the phone smells of burning.

Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.

iPhone camera visual tied to the When to Stop and Get Help section of this guide
iPhone camera visual tied to the When to Stop and Get Help section of this guide

How to Prevent a Repeat

Keep the lens clean, keep a comfortable storage margin, and update iOS when a point release appears rather than months later. Review camera permissions after installing a new social app, and check that a new case leaves the lens and sensors fully clear before you rely on it. A short monthly check of storage, permissions, and case fit prevents most camera faults from ever reaching the black screen stage.

A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.

iPhone camera visual tied to the How to Prevent a Repeat section of this guide
iPhone camera visual tied to the How to Prevent a Repeat section of this guide

More Reading on Stratilyze

More Reading on Stratilyze. If this guide helped, the related guides on this site cover the neighbouring faults that often appear alongside this one, including Fix Iphone No Sound, Fix Iphone Face Id Not Working and Fix Iphone Battery Draining Fast. Reading the closest match first usually saves a second round of troubleshooting, because a fault in one feature often shares a cause with a fault in another. Keep this guide open while you check the related one, and compare the symptom tables before changing any setting, since the right fix depends on matching your exact symptom rather than the closest headline.

Working the List a Second Time

A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.

During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.

Confirming Normal Behaviour Before You Stop

Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.

The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.

Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.

Frequently Asked Questions

Why did this problem start suddenly?

The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.

How long should each fix take before I move on?

Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.

Will clearing data or resetting settings delete my content?

Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.

What if the fault affects only one app, one device, or one connection?

That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix iPhone camera not working helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.

When should I contact support instead of trying more fixes?

Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.

How do I stop this happening again?

Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.

The Sensible Place to Stop

Work through fix iPhone camera not working in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.

Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.

iPhone camera visual tied to the The Sensible Place to Stop section of this guide
iPhone camera visual tied to the The Sensible Place to Stop section of this guide

Leave a Comment