Fujifilm FinePix S8200 vs Canon PowerShot SX510 HS

Winner
Fujifilm FinePix S8200

54

Canon PowerShot SX510 HS

47

Runner-up

Reasons to buy the Fujifilm FinePix S8200

Wide aperture
Aperture
f/2.9
High speed movies
High-speed framerate
480 fps
High ISO
Light sensitivity
12,800 ISO
In-camera HDR
HDR
Combines multiple exposures
 

Reasons to buy the Canon PowerShot SX510 HS

Size
Really small
Standard size (104×70×80 mm)
Supports 24p
24p movies
For that film look
High-speed framerate
High speed movies
240 fps
Sensor type
CMOS Sensor
Better in low light

galleries

Explore our gallery of 50 sample photos taken by the Canon PowerShot SX510 HS.
Explore our gallery of 5 sample photos taken by the Fujifilm FinePix S8200.

competitors

Fujifilm FinePix S8200 Competitors

Sony CyberShot DSC-H300

Sony CyberShot DSC-H300

Super zoom

$178 - $190

Weight Lighter
Longest exposure Significantly longer exposures
High-speed framerate Doesn't record high-speed movies
Fujifilm FinePix S8600

Fujifilm FinePix S8600

Super zoom

$220

Size Significantly smaller
Thickness Significantly thinner
High-speed framerate Doesn't record high-speed movies
Nikon Coolpix L820

Nikon Coolpix L820

Super zoom

$275

Screen resolution Significantly higher resolution screen
Size Smaller
High-speed framerate Lower speed movies

Canon PowerShot SX510 HS Competitors

Canon PowerShot SX410 IS

Canon PowerShot SX410 IS

Super zoom

$160 - $179

Zoom More zoom
Fastest shutter speed Much faster max shutter speed
High-speed framerate Doesn't record high-speed movies
Canon PowerShot SX530 HS

Canon PowerShot SX530 HS

Super zoom

$270 - $279

Zoom Significantly more zoom
Autofocus Faster autofocus
High-speed framerate Doesn't record high-speed movies
Sony CyberShot DSC-H300

Sony CyberShot DSC-H300

Super zoom

$178 - $190

Aperture Wider aperture
Zoom More zoom
High-speed framerate Doesn't record high-speed movies

discussion

Fujifilm FinePix S8200
FinePix S8200
Fujifilm

Report a correction
Canon PowerShot SX510 HS
PowerShot SX510 HS
Canon

Report a correction

Showing 0 comments