Updated (September 2011): Compare the Nikon D5100 vs Nikon 1 J1

Nikon D5100 vs Nikon 1 J1

Winner
Nikon D5100

49

Nikon 1 J1

30

Runner-up

Reasons to buy the Nikon D5100

Wide dynamic range
Dynamic range
13.6 EV
Flip-out screen
Screen flips out
Great for movies
In-camera HDR
HDR
Combines multiple exposures
Self cleaning sensor
Sensor cleaning
Avoids dust in your photos
 

Reasons to buy the Nikon 1 J1

Size
Really small
Compact (106×61×30 mm)
High-speed framerate
High speed movies
1,200 fps
Continuous shooting
Rapid fire
60 fps
Shutter lag
Barely any delay taking photos
94 ms shutter lag

galleries

Explore our gallery of 50 sample photos taken by the Nikon D5100.
Explore our gallery of 46 sample photos taken by the Nikon 1 J1.

competitors

Nikon D5100 Competitors

Nikon D3300

Nikon D3300

Entry-level DSLR

$419 body only

$399 - $447 with 18-55mm lens

Panorama Can create panoramas in-camera
True resolution Higher true resolution
HDR Lacks in-camera HDR
Nikon D3200

Nikon D3200

Entry-level DSLR

$393 body only

$426 with 18-55mm lens

True resolution Higher true resolution
Color depth Better color depth
HDR Lacks in-camera HDR
Nikon D5300

Nikon D5300

Entry-level DSLR

$411 - $597 body only

$479 - $697 with 18-55mm lens

Screen size Significantly larger screen
GPS Has a GPS
Battery life Slightly shorter battery life

Nikon 1 J1 Competitors

Nikon 1 J5

Nikon 1 J5

Mirrorless interchangeable-lens

$380 - $497 with 10-30mm lens

Screen resolution Significantly higher resolution screen
Dynamic range More dynamic range
High-speed framerate Lower speed movies
Nikon 1 V1

Nikon 1 V1

Mirrorless interchangeable-lens

$495 body only

$700 with 10-30mm lens

Screen resolution Higher resolution screen
External mic jack Has an external mic jack
Autofocus Slower autofocus
Nikon 1 S1

Nikon 1 S1

Mirrorless interchangeable-lens

$440 with 11-2mm lens

Dynamic range More dynamic range
Weight Slightly lighter
Color depth Worse color depth

discussion

Nikon D5100
D5100
Nikon

Report a correction
Nikon 1 J1
1 J1
Nikon

Report a correction

Showing 0 comments