Updated (January 2012): Compare the Canon Powershot S100 vs Panasonic Lumix DMC-ZS15

Canon Powershot S100 vs Panasonic Lumix ZS15

Winner
Canon Powershot S100

57

Panasonic Lumix DMC-ZS15

37

Runner-up

Reasons to buy the Canon Powershot S100

Really small
Size
Compact (99×60×28 mm)
High speed movies
High-speed framerate
240 fps
24p movies
Supports 24p
For that film look
Thin
Thickness
1.1"
 

Reasons to buy the Panasonic Lumix ZS15

Zoom
Great zoom
16x
Fastest shutter speed
Fast shutter speed
1/4000 of a second
Longest exposure
Long exposures
60 seconds

galleries

Explore our gallery of 49 sample photos taken by the Canon Powershot S100.
Explore our gallery of 7 sample photos taken by the Panasonic Lumix DMC-ZS15.

competitors

Canon Powershot S100 Competitors

Canon PowerShot S110

Canon PowerShot S110

Pro digicam

$299

Touch screen Has a touch screen
Light sensitivity Better maximum light sensitivity
GPS No built-in GPS
Canon PowerShot S120

Canon PowerShot S120

Pro digicam

$580

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

Canon PowerShot SX620 HS

Travel zoom

$258 - $259

Zoom Much more zoom
Screen resolution Higher resolution screen
High-speed framerate Doesn't record high-speed movies

Panasonic Lumix DMC-ZS15 Competitors

Panasonic Lumix DMC-ZS10

Panasonic Lumix DMC-ZS10

Travel zoom

$525

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

Panasonic Lumix ZS20

Travel zoom

$639

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

Canon PowerShot SX220 HS

Travel zoom

$274

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

discussion

Canon Powershot S100
Powershot S100
Canon

Report a correction
Panasonic Lumix DMC-ZS15
Lumix ZS15
Panasonic

Report a correction

Showing 0 comments