Updated (February 2012): Compare the Canon PowerShot SX260 HS vs Panasonic Lumix DMC-ZS15

Canon PowerShot SX260 HS vs Panasonic Lumix ZS15

Winner
Canon PowerShot SX260 HS

55

Panasonic Lumix DMC-ZS15

48

Runner-up

Reasons to buy the Canon PowerShot SX260 HS

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

Reasons to buy the Panasonic Lumix ZS15

Continuous shooting
Rapid fire
10 fps
Fastest shutter speed
Fast shutter speed
1/4000 of a second
Longest exposure
Long exposures
60 seconds

galleries

Explore our gallery of 50 sample photos taken by the Canon PowerShot SX260 HS.
Explore our gallery of 7 sample photos taken by the Panasonic Lumix DMC-ZS15.

competitors

Canon PowerShot SX260 HS Competitors

Canon PowerShot SX280 HS

Canon PowerShot SX280 HS

Travel zoom

$315

Light sensitivity Better maximum light sensitivity
Lowest price Cheaper
Supports 24p No 24p support
Canon PowerShot SX720 HS

Canon PowerShot SX720 HS

Travel zoom

$275 - $329

Zoom Much more zoom
Screen resolution Higher resolution screen
GPS No built-in GPS
Canon PowerShot SX240 HS

Canon PowerShot SX240 HS

Travel zoom

$170

Battery life Longer battery life
Lowest price Cheaper
GPS No built-in GPS

Panasonic Lumix DMC-ZS15 Competitors

Panasonic Lumix DMC-ZS10

Panasonic Lumix DMC-ZS10

Travel zoom

$525

GPS Has a GPS
High-speed framerate Records high-speed movies
Light sensitivity Worse maximum light sensitivity
Panasonic Lumix DMC-ZS20

Panasonic Lumix ZS20

Travel zoom

$639

GPS Has a GPS
High-speed framerate Records high-speed movies
Longest exposure Much shorter max exposures
Canon PowerShot SX220 HS

Canon PowerShot SX220 HS

Travel zoom

$275

High-speed framerate Records high-speed movies
Supports 24p Supports 24p
Wide angle Significantly worse wide angle

discussion

Canon PowerShot SX260 HS
PowerShot SX260 HS
Canon

Report a correction
Panasonic Lumix DMC-ZS15
Lumix ZS15
Panasonic

Report a correction

Showing 0 comments