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

Nikon Coolpix P310 vs Canon PowerShot SX260 HS

Nikon Coolpix P310
Canon PowerShot SX260 HS

Reasons to buy the Nikon Coolpix P310

Wide aperture
Aperture
f/1.8
High resolution screen
Screen resolution
921k dots
Many focus points
Focus points
99
 

Reasons to buy the Canon PowerShot SX260 HS

High-speed framerate
High speed movies
240 fps
Supports 24p
24p movies
For that film look
GPS
Built-in GPS
Great for travel
Fastest shutter speed
Fast shutter speed
1/3200 of a second

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 P310.

competitors

Nikon Coolpix P310 Competitors

Nikon Coolpix P300

Nikon Coolpix P300

Pro digicam

$491

High-speed framerate Records high-speed movies
Continuous shooting Shoots faster
Lowest price More expensive
Nikon Coolpix P340

Nikon Coolpix P340

Pro digicam

$349

High-speed framerate Records high-speed movies
Continuous shooting Shoots faster
Battery life Slightly shorter battery life
Canon Powershot S100

Canon Powershot S100

Pro digicam

$369

High-speed framerate Records high-speed movies
Supports 24p Supports 24p
Focus points Many fewer focus points

Canon PowerShot SX260 HS Competitors

Canon PowerShot SX610 HS

Canon PowerShot SX610 HS

Travel zoom

$198 - $249

Screen resolution Significantly higher resolution screen
Size Smaller
High-speed framerate Doesn't record high-speed movies
Canon PowerShot SX720 HS

Canon PowerShot SX720 HS

Travel zoom

$314 - $379

Zoom Much more zoom
Screen resolution Significantly higher resolution screen
High-speed framerate Doesn't record high-speed movies
Canon PowerShot SX280 HS

Canon PowerShot SX280 HS

Travel zoom

$329

Light sensitivity Better maximum light sensitivity
Lowest price Cheaper
Supports 24p No 24p support

discussion

Nikon Coolpix P310
Coolpix P310
Nikon

Report a correction
Canon PowerShot SX260 HS
PowerShot SX260 HS
Canon

Report a correction

Showing 0 comments