The short answer
Plates blur for three connected reasons. Motion blur: when the shutter stays open too long, a fast-moving plate smears across the frame. Low bitrate: when the encoder is given too little data per second, it discards fine detail to keep the file size down. And low light: the camera lengthens exposure to collect more light, which makes motion blur worse. Frame rate affects smoothness and the chance of catching a clean frame, while bitrate affects how much detail survives compression. Resolution sets the maximum detail, but these three decide how much of it you actually see when you pause the video and zoom in. The order of operations for a buyer is therefore fixed: confirm the sensor and chipset, then judge the settings that turn them into files, because the first pair sets the ceiling and the second decides how close the camera gets.
Frame rate
Frame rate is the number of pictures recorded each second. Most dash cams record 30 frames per second, a few offer 60, and some stretch lower frame rates to save space in specific modes such as time-lapse parking. A higher frame rate gives more chances that one frame is sharp at the moment a plate passes, and makes motion look smoother. It also doubles the data and the processing load compared with 30fps, which is why many 4K recorders cap at 30fps, with the Novatek NT96670 class recording 2160P at 30fps. Many buyers are better served by 1080P or 1440P at a higher frame rate than 4K at 30fps, particularly for fast-moving scenes; the right answer depends on the use case. Lower frame rates appear deliberately in parking modes, where time-lapse recording trades smoothness for hours of coverage on a small card. That is a sensible trade for surveillance and a poor one for evidence of a moving collision, which is why the two modes belong to different settings rather than one number.
Shutter speed: the hidden setting
Shutter speed is the exposure time per frame, and it is the setting most responsible for blur. It is rarely published, because the camera adjusts it automatically. In daylight the shutter is short and plates are crisp; at dusk the exposure lengthens and anything fast becomes streaky. The same sensor and chipset can behave very differently depending on exposure tuning, which is one reason two cameras with identical headline specs perform differently at night. Wide-aperture lenses and low-light sensors help by gathering more light per millisecond; see the image sensor note. Judge night footage at the speeds your customers actually drive, because a clip recorded at low speed flatters the shutter and hides exactly the blur that appears at road speed.
Bitrate and compression
Bitrate is the amount of data written per second of video. The encoder compresses each frame by discarding detail the eye is least likely to notice, and the lower the bitrate, the more aggressive that discarding becomes. Fine, high-contrast detail such as plate characters is exactly the kind of thing that compression softens first. A 4K clip at a very low bitrate may look worse at 100 percent zoom than a 1080P clip with a generous bitrate. Spec sheets often list only a range or omit bitrate entirely, so ask for the default value and the maximum value, and judge by sample files. Ask for the average file size per minute in each recording mode, in writing; it converts directly into card sizing and loop length for your customers, a calculation set out in how much storage a dash cam needs.
| Factor | What it controls | Effect on plates | Where to check |
|---|---|---|---|
| Resolution | Pixels per frame | Sets the maximum detail | Spec sheet and sensor model |
| Frame rate | Frames per second | More chances of a sharp frame | Spec sheet, recording modes |
| Shutter speed | Exposure time | Longer exposure causes motion blur | Sample footage at dusk and night |
| Bitrate | Data per second | Low bitrate softens fine detail | Supplier settings, file size |
| Codec | Compression method | H.265 saves space at similar quality | Spec sheet, menu options |
How the codec fits in
The codec determines how efficiently bitrate is spent. H.265 delivers similar visual quality at roughly half the storage of H.264, so a camera can either save space or spend the same bitrate on more detail. Cheaper recorders may offer H.265 but cap the bitrate low, so the codec label alone is not proof of good quality. The full comparison is in H.265 vs H.264. Card speed also matters: if the card cannot keep up with writes at a high bitrate, the recorder drops frames or stops, and the footage has gaps. Choose a rated high-endurance card, as in the SD card line. Where a recorder offers both codecs, compare file sizes on the same scene before choosing the default for your program, since the savings should show up in the card rather than disappear into a lower bitrate.
Testing for plate readability
A repeatable test beats a spec sheet, and the test belongs to whoever signs off the program: keep the clips and notes with the sample approval record so the production specification inherits the findings, and repeat the routine when a platform or sensor change is proposed. Roadtrace recommends this routine for samples:
- Mount the sample at the intended position and record the same road at midday, dusk and night.
- Include a plate at a known distance, in both the same lane and the adjacent lane, with the car moving at a steady speed.
- Export the file untouched; pause on the frame where the plate is largest and zoom to 100 percent.
- Repeat with the default settings and with the maximum bitrate setting if the menu offers one.
- Note which frames are readable and in what conditions; attach the clips to the sample approval record.
This is a comparison tool, not a certified measurement. Write conclusions as observations from the sample, and never promise a customer a readable plate in every condition. The sample checklist shows where this test fits.
What to put in the specification
For an OEM or private-label program, list the recording modes by resolution, frame rate and default bitrate, and require that production units match the approved sample. Ask which settings can be changed by the end user and which are locked by firmware. If you are building a product range, the technology overview and the resolution guide give the context; send the specification through the quote form to receive a written shortlist.
For bundles, the same logic applies to the card: a high write load at a high bitrate justifies the high-endurance rating on the card you ship in the box, and the card choice should be frozen in the specification next to the recording mode.