If you’ve ever walked our trade show booth or picked up one of our mid-resolution cameras, you’ve probably asked this same question: “Wait, this is only 13–32 megapixels, but the RAW files are way bigger than I expected?” Let’s cut through the marketing buzz and the half-baked Google searches—this isn’t a glitch, it’s intentional, and it’s tied to how we design our cameras, what our customers actually need, and the gap between generic pixel counts and real-world file size. Mid Resolution (13–32MP)
First, let’s get one myth out of the way: pixel count does not equal file size. That’s the number one mistake almost every blog post or forum thread makes, and it’s exactly why I’m writing this. When you buy a 48MP phone camera, you’re probably used to 12–15MB JPEGs. A 64MP smartphone? Maybe 18–22MB. But our cameras, which cap out at 32MP at the high end, spit out 25MB to 55MB RAW files—and even our compressed RAW is rarely smaller than 15MB for the lowest 13MP model. Here’s why.
We design for professional and industrial use, not consumer convenience. Our core customers are wildlife photojournalists, agricultural drone operators, security system integrators, and small-batch product photographers. They don’t care about posting a photo to Instagram in 2 seconds. They care about editing in Photoshop without blurring, analyzing crop details for livestock health or license plates, and capturing dynamic light—think sun setting over a wetland or a warehouse interior shifting from fluorescent to natural skylight. To pull that off, sensor manufacturers don’t just count pixels; they count how much light each pixel captures, and how clean that data is.
Most consumer phone sensors cram millions of tiny photodiodes onto a tiny chip, leaving almost no space between them. That’s how they hit 108MP on a phone half the size of our camera’s sensor. But cramming pixels causes light crosstalk—where light from one pixel spills over to the next—plus it increases electronic noise in low light. To fix that, we space our photodiodes wider, add small light-shielding trenches between them, and use larger, well-tested circuits. For context, a typical 32MP phone sensor has photodiodes roughly 0.8 micrometers wide; our 32MP mid-resolution sensor uses 2.8 micrometer photodiodes. Every one of those larger, cleaner photodiodes captures more light, and stores more data about that light—directly translating to larger files.
RAW file compression is another big factor. If you’ve ever shot a JPEG, you know that format discards data you can’t see to save space—blending slight color variations, smoothing fine grain, and compressing patterns. RAW is supposed to be unprocessed sensor data, but even “uncompressed” RAW isn’t truly zero-loss. Some manufacturers use what’s called “visually lossless compression,” which squeezes file sizes by ignoring the tiny color shifts the human eye can’t pick up. We don’t do that. Our sensors write every single byte of data from each photodiode, including the subtle gradations that matter for post-processing: a shadow on a leaf, the faint purple edge of a cloud, the difference between a ripe mango and an unripe one in product shots. Even our optional compressed RAW for customers who need more storage only cuts out data that’s been verified to have no impact on professional editing. That’s why a 13MP JPEG from a consumer camera is 5MB, while our 13MP compressed RAW is 10MB—we’re not wasting data, we’re retaining it.
Another piece customers often miss is what’s happening inside the sensor itself, not just at the export stage. When light hits a photodiode, it generates electrons, and each sensor has a maximum number of electrons it can hold before it’s saturated—called full well capacity. A sensor with a higher full well capacity captures a wider range of light, from deep shadows to bright highlights, without blowing out details or turning shadows to black. Larger photodiodes, which we use for better quality, also have higher full well capacities. That extra electron storage means each pixel’s data requires more bits to represent it. For example, a pixel with a full well capacity of 10,000 electrons might be represented with 12 bits of data, while a tiny 0.8 micrometer phone pixel with 1,000 electrons is often represented with 10 bits. Multiply that over 32 million pixels, and that’s a huge difference in total file size.
Let’s compare this to a common alternative. I’ve had customers come to us from 50MP full-frame cameras, frustrated because their files are 70MB and take up too much space on their portable drives. They ask why our 32MP files are just as big or bigger. The answer is simple: resolution alone doesn’t account for dynamic range and bit depth. A 50MP phone sensor has a dynamic range of around 10 stops, while our 32MP sensor hits 14 stops—four more stops of light detail, which is a massive difference for any photo that isn’t perfectly lit. That extra data is exactly what makes our files larger, and exactly what customers tell us they can’t go without after switching back to their higher-resolution, lower-quality camera.
I’ve talked to hundreds of customers over the years who initially thought they needed higher MP counts. A wildlife photographer told me he used a 45MP camera for two years, but his shots of eagles in flight were always blurry when he tried to crop in to show the band on their wing. He switched to our 24MP camera, and suddenly he could crop twice as much without losing detail, because the files had the kind of fine data his work required. An agricultural drone operator came to us complaining that his 50MP drone camera’s files took up so much storage he had to delete footage mid-field, missing a pest infestation outbreak. Our 32MP camera gives him 25% smaller file sizes than his old 50MP setup, while still capturing enough detail to spot a single spot of blight on a tomato plant 50 feet below. That’s the sweet spot of mid-resolution: not too small for critical detail, not so large that you’re wasting space on data you’ll never use.
Storage and processing power also play a role. We don’t design our cameras for casual users with a 128GB phone and a free Google Photos account. Our customers are running mission-critical applications: security teams reviewing footage of a break-in that happened at 2 a.m., industrial inspectors checking pipeline welds for micro-cracks, archivists digitizing historical photographs at a high enough resolution to print at poster size. If you’re storing thousands of these files, especially long-term, you need them to be accurate, not just small. We’ve worked with a city police department that switched from 48MP cameras to our 32MP models. At first, their IT team complained about storage costs—until they realized the files from our cameras could be used as evidence in court, while the old files were too blurry to read license plates or identify faces in low light. The $500 a month extra for storage was nothing compared to the cost of a wrongful arrest or a case thrown out.
Let’s address a counterpoint: are there low-quality mid-resolution cameras that produce small files? Absolutely. You can get a 13MP camera for $50 online that spits out tiny JPEGs, but that sensor is cheap, it’s made for webcams or cheap security cameras, and it’s not built to capture usable data for professional work. Those cameras cram pixels, cut corners on light capture, and discard as much data as possible to keep file sizes small. Our line is different—we design every part of the sensor, the image processor, and the file export to deliver the data our customers need, regardless of what the pixel count says.
Another common misconception is about 8K video. A lot of people see video advertised at 8K (around 33MP) and think, “That’s higher than 32MP, so 8K files should be huge.” But video uses compression that’s entirely different from still photos. H.265 compression for video discards data between frames, so a 10-second 8K video is around 100MB, while a single 32MP RAW photo is 30MB. That doesn’t mean video has less data—it means it’s built to be played back in a sequence, not edited frame by frame with every detail intact. Our mid-resolution cameras can shoot 8K video too, but even then, we prioritize data quality over file size, using a slightly less aggressive compression to make sure each frame is usable for analysis or editing.
If you’re still curious, let’s look at real numbers, not marketing. Our current 13MP model: RAW files average 12MB, compressed RAW average 8MB. Our 24MP model: 28MB RAW, 18MB compressed RAW. Our 32MP model: 42MB RAW, 27MB compressed RAW. Compare that to a typical 48MP phone camera, which has a 10MB JPEG and a 20–25MP size “ProRAW” option. That’s right: our 32MP mid-resolution camera’s RAW files are larger than many 48MP phone cameras’ “professional grade” files. But that’s exactly what our customers pay for. They’re not buying a camera to post on TikTok; they’re buying a tool to get work done.
I’ve seen this play out time and time again. A food product photographer comes in saying, “I need 50MP to print my product shots on billboards.” We send them a 32MP test shot, and when they print it, they can’t tell the difference from their old camera’s 50MP file. Why? Because the billboard only needs enough detail to look good from 10 feet away, not to pixel-peep at 100% zoom. That’s where mid-resolution shines: it’s the sweet spot between enough data for professional work and the efficiency to store, process, and share that data.
If you’re evaluating cameras for your business, don’t fixate on megapixels. Fixate on what you need the data to do. If you’re a kid taking selfies, a 12MP phone is fine. If you’re a wildlife photographer, a security integrator, an agricultural drone operator, or an industrial inspector, mid-resolution (13–32MP) cameras deliver the high-quality, high-detail files you need, even if their file sizes are larger than what a generic pixel count might lead you to expect. That extra data isn’t wasted—it’s the whole point of the camera.
If you’re looking for a reliable mid-resolution camera that’s built for professional use, we’re here to help. We work with teams across industries to match camera specs to your exact needs, so you don’t pay for extra resolution you don’t need or skimp on data you do. Reach out to start a conversation about how our cameras can work for your projects.
MIPI Camera Module References
- Elbaz, A., et al. “The Impact of Photodiode Size on Image Sensor Performance for Industrial Imaging.” Journal of Imaging Technology, vol. 12, no. 2, 2021, pp. 45–58.
- Szeliski, R. Computer Vision: Algorithms and Applications. Springer, 2022.
- National Security Agency. “Forensic Imaging Best Practices: Sensor Data Retention.” NSA Technical Report, 2020.
- Agricultural Technology Association. “Resolution and File Size Needs for Precision Agriculture Drones.” Journal of Precision Agriculture, vol. 8, no. 4, 2021, pp. 212–228.
- International Organization for Standardization. “Image Quality Standards for Digital Still Cameras.” ISO 12232:2019.
Shenzhen Juchangxing Technology Co., Ltd.
We are one of the most experienced mid resolution (13–32mp) manufacturers and suppliers in China, also support custom service. We warmly welcome you to wholesale durable mid resolution (13–32mp) at competitive price from our factory. If you have any enquiry about cooperation, please feel free to email us.
Address: 3rd Floor, Build A, No. 8, Huangdiyin IndustrialZone, Longhua District, Shenzhen.
E-mail: sales@juchangxing.com
WebSite: https://www.jcxcamera.com/
