Camera Pixels-Per-Foot Identification Calculator
Check whether a security camera view has enough pixels per foot for detection, recognition, or identification by combining horizontal pixels, scene width, distance, lens angle, and usable detail loss.
🎯Identification presetsPick a camera view, then adjust the numbers.
⚙Calculator inputsPPF = horizontal pixels / scene width in feet.
📌Current view specsLive values from the selected camera view.
Identification results
🖼DORI comparison gridWhat each density is usually good for.
Person or object is present in the scene. Good for wide awareness views.
Activity, movement, clothing color, and general body cues become more useful.
Known people, vehicles, or repeated visitors may be recognized in clean footage.
Higher-detail face or plate planning level under favorable lighting and focus.
📋PPF reference tablesDORI thresholds, resolution, FOV, and project sizes.
| DORI level | PPM | PPF equivalent | Planning meaning |
|---|---|---|---|
| Detect | 25 PPM | 7.6 PPF | Detect that a person-sized target is present. |
| Observe | 63 PPM | 19.2 PPF | See useful activity and broad descriptive detail. |
| Recognize | 125 PPM | 38.1 PPF | Recognize a known person or familiar object. |
| Identify | 250 PPM | 76.2 PPF | Plan for identification detail in favorable footage. |
| High detail | 375 PPM | 114.3 PPF | Add extra margin for difficult views or tighter evidence goals. |
| Stream width | Common label | Width at 76 PPF | Best use |
|---|---|---|---|
| 1280 px | 720p | 16.8 ft | Narrow entries and short hall views. |
| 1920 px | 2MP / 1080p | 25.2 ft | Door, porch, or single-lane views. |
| 2560 px | 4MP | 33.6 ft | Small driveway or garage detail. |
| 3840 px | 8MP / 4K | 50.4 ft | Wider ID view when optics and light are good. |
| 5120 px | 12MP | 67.2 ft | Large scene, if recorded stream preserves detail. |
| HFOV angle | Width at 25 ft | 4MP raw PPF | Camera view |
|---|---|---|---|
| 25° | 11.1 ft | 231 PPF | Gate, lane, or choke point. |
| 40° | 18.2 ft | 141 PPF | Entry path or side corridor. |
| 60° | 28.9 ft | 89 PPF | Single driveway detail. |
| 90° | 50.0 ft | 51 PPF | Wide porch or two-car overview. |
| 110° | 71.4 ft | 36 PPF | Awareness view, not strong ID. |
| Common view | Scene width | Reasonable goal | Planning note |
|---|---|---|---|
| Front door face path | 5 to 8 ft | Identify | Tight framing gives strong PPF from modest cameras. |
| Single driveway lane | 10 to 14 ft | Identify | Narrow the lens angle before relying on more pixels. |
| Two-car driveway | 20 to 28 ft | Recognize | Use a separate entry camera for face detail. |
| Backyard overview | 45 to 80 ft | Detect | Good for activity, weak for identification. |
| Side corridor | 4 to 8 ft | Identify | Excellent ID candidate if angle and light are controlled. |
🧮Formula tableHow the calculator verifies the result.
| Calculation | Formula | Units | Use |
|---|---|---|---|
| Scene width from lens angle | Width = 2 x distance x tan(HFOV / 2) | feet or meters | Find the real horizontal coverage at target distance. |
| Pixels per foot | PPF = horizontal pixels / scene width ft | pixels/ft | Main identification density check. |
| Pixels per meter | PPM = horizontal pixels / scene width m | pixels/m | DORI thresholds are commonly published in PPM. |
| Effective PPF | Raw PPF x angle factor x usable factor x zoom factor | pixels/ft | Allows for view angle, detail loss, and crop. |
| Goal distance | Distance = pixels / (target PPF x 2 x tan(HFOV / 2)) | feet or meters | Maximum geometric distance for the selected goal. |
💡Identification planning tips
This calculator is for camera planning and layout comparison. Identification quality still depends on lighting, shutter speed, focus, lens quality, compression, weather, subject angle, and the recorded stream settings.
So you’ve selected your camera resolution after hours of thinking it over. You mounted it perfectly level at just the right height. But no one looked at pixels per foot.
What’s the difference? The marketing number is called resolution, the reality check is pixels per foot. That number will tell you how many actual details land on the ground compared to how big something you’re trying to see is. If you spread three thousand pixels over a hundred-foot wide yard, each person in that image are represented by only about thirty pixels. You can’t identify them with that little. In fact, you might not even be able to tell the difference between a human and a large dog.
Why Pixels Per Foot Matters More Than Resolution
All you have to do is enter the distance and the angle of your lens, and the calculator will spit out an answer, no need to guess about whether your lenses is covering the ground you believe them to cover. The reason most folks assume a “four K” camera can see a face anywhere is because they don’t realize that there’s no such thing as a free lunch here; there’s a reason that optics has never been free, and it’s called physics. There’s a finite amount of information contained within an image circle created by a lens, and it’s up to the lens to distribute this across the image.
As you increase the field of view to be able to see more of your driveway, you’re stretching these pixels further apart. You get more awareness, sure, but less detail. It’s an unavoidable tradeoff, and it doesn’t care how big or small your sensor is. If the scene expands horizontally but the number of pixels stay the same, the density decreases.
You’re giving up resolution to get more coverage; that exchange is where a security system becomes one that gives you evidence rather than just a vague impression of motion. These are usable details. We account for real-world installations, such as reduced usable detail and loss from the mounting angle. Most houses will need side shots or downward angles to cover entry points. Straight down keeps the geometry intact. However, when the target plane is not perpendicular, it starts to distort the image. Faces start to foreshorten and shoulders shrinks. This leads to a falling effective resolution despite having a high number of pixels.
To model this, the calculator allows you to enter a percentage loss. This forces you to face the reality that your perfect spec on paper won’t work in the real world, given where the lens is positioned on the wall. You have to design for the worst case, not the idealized drawing.
For example, there are industry standard benchmarks called DORI thresholds (what is detection vs. Identification). Very few pixels is needed to detect motion. More pixels are required to observe color on clothes. It requires even more pixels to recognize a familiar face. True identification requires about seventy-six pixels per foot. This isn’t some random number pulled out of thin air; it is derived from decades of research into surveillance. That research determine exactly how much data an analytic software program or the human eye require to identify distinct features of a face.
So if you plug those numbers into your calculation and find that you’re not hitting 76 per foot at the distance you want to watch, well, no amount of marketing hyperbole is going to change that fact. Either get closer with the camera/lens, narrow the field down, or concede that you’re just seeking detection.
The trick is generally pulling the correct lever, which is typically the choice of lens focal length. Wide angle gets more coverage but lowers pixel concentration. Capturing and then digitally zooming in doesn’t add anything; it simply enlarges the fuzziness. Switching to a narrower varifocal lens, or using optical zoom, narrows the framing and concentrates those pixels into a smaller space. That greatly increases the effective range without modifying the camera itself. In many cases replacing the lens is easier and less expensive than buying a whole new system.
The embedded reference tables with this tool show that minor variations in field of view radically affect your effective range. Ten degrees might be the difference between reading a license plate vs. Seeing a form. Which is why planning on a margin helps; lighting and compression will nibble away at your usable detail as well. You may achieve recognition rather than identification in the glare of night time conditions or under a heavy video encoder’s hand, yet that doesn’t mean you don’t pick up any clues that help whittle down suspects. It does mean you planned for detection, while getting less.
Planning for evidence means aligning your optics choices with what you actualy need. Don’t try and watch your fifty-foot wide backyard perimeter with a four-k camera hoping to ID bad guys. Use it to guard some single entry point where the geometry lets the pixels fall densely enough to count. So begin by measuring out the size of the scene you want to cover, then work backward up the chain until you reach a lens whose pixel density exceeds the line. It’s easy math, the rigor to actually do it is what distinguishes useful security from overpriced decoration.
Once you stop chasing megapixels and focus on pixels per foot, the image starts to make sense.