Updated (September 2011): Compare the Canon Powershot S100 vs Casio Exilim EX-FH100

Canon Powershot S100 vs Casio Exilim EX-FH100

Winner
Canon Powershot S100

56

Casio Exilim EX-FH100

38

Runner-up

Reasons to buy the Canon Powershot S100

Really small
Size
Compact (99×60×28 mm)
24p movies
Supports 24p
For that film look
Great macro
Macro focus
3.0 cm
Light-weight
Weight
198 g
 

Reasons to buy the Casio Exilim EX-FH100

High-speed framerate
High speed movies
1,000 fps
Longest exposure
Long exposures
30 seconds
Size
Really small
Compact (104×60×28 mm)
Thickness
Thin
1.1"

galleries

Explore our gallery of 49 sample photos taken by the Canon Powershot S100.
Explore our gallery of 3 sample photos taken by the Casio Exilim EX-FH100.

competitors

Canon Powershot S100 Competitors

Canon PowerShot S110

Canon PowerShot S110

Pro digicam

$330

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

$449 - $515

Touch screen Has a touch screen
Screen resolution Significantly higher resolution screen
Supports 24p No 24p support
Sony Cybershot DSC-RX100

Sony Cybershot DSC-RX100

Pro digicam

$498

Overall image quality Significantly better image quality
Screen resolution Much higher resolution screen
High-speed framerate Doesn't record high-speed movies

Casio Exilim EX-FH100 Competitors

Casio Exilim EX-FH20

Casio Exilim EX-FH20

Super zoom

$1,462

Zoom More zoom
Aperture Wider aperture
Size Much larger
Panasonic Lumix DMC-LX3

Panasonic Lumix DMC-LX3

Pro digicam

$300

Aperture Significantly wider aperture
Macro focus Much better macro capability
High-speed framerate Doesn't record high-speed movies
Sony Cyber-shot DSC-H2

Sony Cyber-shot DSC-H2

Super zoom

$259

Macro focus Much better macro capability
Aperture Wider aperture
High-speed framerate Doesn't record high-speed movies

discussion

Canon Powershot S100
Powershot S100
Canon

Report a correction
Casio Exilim EX-FH100
Exilim EX-FH100
Casio

Report a correction

Showing 0 comments