Updated (January 2012): Compare the Fujifilm FinePix XP30 vs Fujifilm FinePix XP50

Fujifilm FinePix XP50 vs Fujifilm FinePix XP30

Tie
Fujifilm FinePix XP50

55

Fujifilm FinePix XP30

53

Tie

Reasons to buy the Fujifilm FinePix XP50

CMOS Sensor
Sensor type
Better in low light
In-camera HDR
HDR
Combines multiple exposures
In-camera panoramas
Panorama
Stitches together multiple photos into a panorama
Built-in flash
Built-in flash
Usually standard
 

Reasons to buy the Fujifilm FinePix XP30

Size
Really small
Compact (99×68×24 mm)
Thickness
Thin
0.9"
Weight
Light-weight
165 g
GPS
Built-in GPS
Great for travel

galleries

Explore our gallery of 15 sample photos taken by the Fujifilm FinePix XP30.
Explore our gallery of 13 sample photos taken by the Fujifilm FinePix XP50.

competitors

Fujifilm FinePix XP50 Competitors

Fujifilm XP80

Fujifilm XP80

Waterproof

$148 - $149

Continuous shooting Shoots much faster
Screen resolution Higher resolution screen
Size Slightly larger
GoPro HERO3 Black Edition

GoPro HERO3 Black Edition

Waterproof

Wide angle Much better wide angle
High-speed framerate Records high-speed movies
Built-in flash No built-in flash
Fujifilm FinePix XP70

Fujifilm FinePix XP70

Waterproof

$110

Continuous shooting Shoots much faster
Screen resolution Higher resolution screen
Size Slightly larger

Fujifilm FinePix XP30 Competitors

Fujifilm X-Pro2

Fujifilm X-Pro2

Mirrorless interchangeable-lens

$1,699 body only

$2,099 with 35mm lens

Light sensitivity Better maximum light sensitivity
Screen resolution Much higher resolution screen
Size Much larger
Fujifilm FinePix XP100

Fujifilm FinePix XP100

Waterproof

$250

Continuous shooting Shoots much faster
Movie format Higher resolution movies
Size Larger
Panasonic Lumix TS25

Panasonic Lumix TS25

Waterproof

$166

Wide angle Significantly better wide angle
Panorama Can create panoramas in-camera
GPS No built-in GPS

discussion

Fujifilm FinePix XP50
FinePix XP50
Fujifilm

Report a correction
Fujifilm FinePix XP30
FinePix XP30
Fujifilm

Report a correction

Showing 0 comments