Does a Content & Privacy Restriction block dual camera recording on iPhone?

Three different reasons a camera app can go dark

Deny an app its own camera permission the first time it asks, and that one app loses access — every other app on the phone, including the stock Camera app, keeps working normally. That is covered in its own guide, because a dual-camera app fails at that in a particular way: there is no fallback, unlike a denied microphone, because video is the entire output.

A Screen Time App Limit or Downtime window works differently again. It does not touch permissions at all — it puts a full-screen block over whichever app is currently open, the instant the budget runs out or the schedule kicks in, and that ends a recording already in progress the same way switching apps does.

A Content & Privacy Restriction with Camera turned off is neither of those. It is not aimed at one app, and it is not a clock running out. It is a single switch that tells iOS the camera hardware itself is off-limits, for anything that might ask, at any time of day.

What turning Camera off under Allowed Apps actually does

The most visible sign is that the Camera app's own icon disappears from the Home Screen and the App Library entirely, not just becomes unusable. That is the clue that this restriction sits below the level of individual apps and their permissions — it is not that the Camera app tried to open and failed, it is that iOS is not presenting the camera to anything at all.

For a third-party app like DualCam, this shows up as a harder kind of failure than a denied permission. Denying camera permission still lets the system acknowledge that a camera exists and that this particular app is not allowed to use it. With the restriction in place, there is nothing to enumerate — no camera device for a capture session to find, so there is no permission prompt to answer and no toggle in that app's own Settings entry that would help, because the block is happening a layer above where app permissions live.

Why there is no shortened file the way there is with a time limit

A Screen Time App Limit interrupts a recording that has already started, so whatever was captured up to that point gets finalized into a complete, playable file — shorter than intended, but not broken. A Content & Privacy Restriction with Camera off never lets that recording start in the first place, for the same reason a device that fails the multi-camera hardware check never produces a frame: without a camera to open, there is no capture session to build, so there is nothing to write and nothing to finalize.

That difference matters for expectations more than anything else. A limit that cuts a take short at least leaves you with something. A restriction that blocks the camera outright means the app never got as far as recording anything, which is worth knowing before assuming a recording somehow went missing.

Who can actually turn it back on

This is the part that separates a Content & Privacy Restriction from the other two causes, and it depends entirely on whose device it is and who set the restriction up.

• On a personal iPhone where you turned Restrictions on yourself, the fix is in Settings > Screen Time > Content & Privacy Restrictions > Allowed Apps, guarded by a separate Screen Time passcode. If you remember that passcode, you can turn Camera back on immediately.
• On a child's iPhone set up through Family Sharing, the same Allowed Apps toggle lives in the parent's Screen Time settings for that child's device, not on the device itself — the child cannot turn it back on locally even with the passcode, because the setting is managed remotely.
• On a school-issued or employer-issued iPhone enrolled in Mobile Device Management, the same kind of camera restriction can be pushed down by a configuration profile rather than set locally at all. There is often no Screen Time passcode to enter on the device, because the setting was never the device holder's to control in the first place — only whoever manages the profile can lift it.