Updated (September 2011): Compare the Canon Powershot S100 vs Nikon 1 V1

Canon Powershot S100 vs Nikon 1 V1

Winner
Canon Powershot S100

64

Nikon 1 V1

34

Runner-up

Reasons to buy the Canon Powershot S100

Image stabilization
Image stabilization
  1. Lens
24p movies
Supports 24p
For that film look
In-camera HDR
HDR
Combines multiple exposures
Built-in GPS
GPS
Great for travel
 

Reasons to buy the Nikon 1 V1

High-speed framerate
High speed movies
1,200 fps
Continuous shooting
Rapid fire
60 fps
Startup delay
Almost no delay when powering up
1300 ms startup delay
Movie continuous focus
Movie continuous focus
Makes it easy to get in-focus movies

galleries

Explore our gallery of 49 sample photos taken by the Canon Powershot S100.
Explore our gallery of 50 sample photos taken by the Nikon 1 V1.

competitors

Canon Powershot S100 Competitors

Canon PowerShot S110

Canon PowerShot S110

Pro digicam

$494

Touch screen Has a touch screen
Startup delay Slightly less startup delay
Shutter lag Significantly more shutter lag
Canon PowerShot S120

Canon PowerShot S120

Pro digicam

$449 - $499

Touch screen Has a touch screen
Screen resolution Higher resolution screen
Supports 24p No 24p support
Canon PowerShot SX720 HS

Canon PowerShot SX720 HS

Travel zoom

$329

Zoom Significantly more zoom
Screen resolution Higher resolution screen
Aperture Much narrower aperture

Nikon 1 V1 Competitors

Nikon 1 J1

Nikon 1 J1

Mirrorless interchangeable-lens

$240 with 10-30mm lens

Autofocus Faster autofocus
Size Smaller
Screen resolution Lower resolution screen
Nikon 1 J5

Nikon 1 J5

Mirrorless interchangeable-lens

$497 with 10-30mm lens

Overall image quality Better image quality
Dynamic range More dynamic range
High-speed framerate Lower speed movies
Nikon 1 V3

Nikon 1 V3

Mirrorless interchangeable-lens

$1,197 with 10-30mm lens

Touch screen Has a touch screen
HDR Has in-camera HDR
Autofocus Slower video autofocus

discussion

Canon Powershot S100
Powershot S100
Canon

Report a correction
Nikon 1 V1
1 V1
Nikon

Report a correction

Showing 0 comments