Updated (February 2012): Compare the Canon PowerShot SX260 HS vs Nikon Coolpix S9100

Canon PowerShot SX260 HS vs Nikon Coolpix S9100

Winner
Canon PowerShot SX260 HS

58

Nikon Coolpix S9100

51

Runner-up

Reasons to buy the Canon PowerShot SX260 HS

Built-in GPS
GPS
Great for travel
Really small
Size
Compact (106×61×33 mm)
Image stabilization
Image stabilization
  1. Lens
24p movies
Supports 24p
For that film look
 

Reasons to buy the Nikon Coolpix S9100

Screen resolution
High resolution screen
921k dots
Continuous shooting
Rapid fire
9.5 fps
Size
Really small
Compact (105×62×35 mm)
High-speed framerate
High speed movies
240 fps

galleries

Explore our gallery of 50 sample photos taken by the Canon PowerShot SX260 HS.
Explore our gallery of 50 sample photos taken by the Nikon Coolpix S9100.

competitors

Canon PowerShot SX260 HS Competitors

Canon PowerShot SX620 HS

Canon PowerShot SX620 HS

Travel zoom

$229 - $230

Zoom More zoom
Size Significantly smaller
GPS No built-in GPS
Canon PowerShot SX220 HS

Canon PowerShot SX220 HS

Travel zoom

$288

Aperture Wider aperture
Size Slightly smaller
GPS No built-in GPS
Nikon Coolpix L340

Nikon Coolpix L340

Super zoom

$130 - $159

Wide angle Much better wide angle
Battery life Much longer battery life
Size Much larger

Nikon Coolpix S9100 Competitors

Canon PowerShot SX170 IS

Canon PowerShot SX170 IS

Travel zoom

$200

Image stabilization Better image stabilization
Battery life Longer battery life
High-speed framerate Doesn't record high-speed movies
Nikon Coolpix S7000

Nikon Coolpix S7000

Travel zoom

$270

Size Significantly smaller
Image stabilization Better image stabilization
High-speed framerate Doesn't record high-speed movies
Nikon Coolpix L620

Nikon Coolpix L620

Travel zoom

$230

Battery life Much longer battery life
Image stabilization Better image stabilization
High-speed framerate Doesn't record high-speed movies

discussion

Canon PowerShot SX260 HS
PowerShot SX260 HS
Canon

Report a correction
Nikon Coolpix S9100
Coolpix S9100
Nikon

Report a correction

Showing 0 comments