Straight answer first: the browser tool on this site returns no shutter count for the Fujifilm X-E1, and ExifTool finds none either. ShutterCount reads Fujifilm counts from one place only — MakerNote tag 0x1438 (ImageCount) — and on every full-size X-E1 RAF we have checked, that tag is not there. Below: what the file does show, why the count is missing, and how to check a used X-E1 without it.
Fujifilm announced the X-E1 in September 2012 as a smaller, simpler sibling of the X-Pro1. It uses the same 16.3 MP APS-C X-Trans CMOS sensor and X mount, but drops the X-Pro1's hybrid optical finder in favour of a 2.36M-dot OLED electronic viewfinder. It started the X-E line that continued with the X-E2, X-E3 and X-E4.
| Specification | Fujifilm X-E1 |
|---|---|
| Announced | September 2012 |
| Sensor | 16.3 MP APS-C X-Trans CMOS (23.6 × 15.6 mm) |
| Viewfinder | 2.36M-dot OLED electronic viewfinder (no optical finder) |
| Shutter speeds | 30 s – 1/4000 s |
| RAW format | RAF — no ImageCount tag (0x1438) found, see below |
| Shutter durability | No rating published by Fujifilm that we could find |
| Browser tool | Model, firmware, capture settings, lens data: yes · shutter count: no |
Fujifilm writes its image counter to the RAF MakerNote as tag 0x1438, which ExifTool calls ImageCount. ExifTool's source notes the tag appearing with X-T1 firmware version 3 in 2014 — well after the X-E1 was designed. On the bodies whose files carry it, ShutterCount reads it directly in the browser.
The X-E1 is not one of them. We ran every full-size X-E1 RAF in our release corpus — complete original files, not the 32 KB snippets bundled with the test suite — through both ShutterCount and ExifTool 13.59. Neither returned a count, because the tag is not in the file. The parser does not guess or substitute another field: when 0x1438 is absent, no number is shown.
| Body | Tag 0x1438 in full-size RAF | Browser tool |
|---|---|---|
| Fujifilm X-E1 | Absent (ExifTool 13.59 agrees) | No count |
| Fujifilm X-E4 | Present | Read; matches ExifTool 13.59 |
| Fujifilm X-T1 | Present | Read; exact below 32,768 only |
On the X-T1 generation the firmware uses the tag's top bit as a marker, so only 15 bits of count are stored; the result card says so when it applies.
exiftool -a -G1 -ImageCount FILE.RAF. An empty result means the tag is absent from your file too.With no count in the file, a buyer has to rely on the camera's condition and, where available, on Fujifilm service:
No. ShutterCount reads Fujifilm counts only from RAF MakerNote tag 0x1438 (ImageCount), and that tag is not in X-E1 RAF files. On every full-size X-E1 RAF in our release corpus, neither ShutterCount nor ExifTool 13.59 found a count. The tool still shows the camera model, firmware version, capture settings and lens data where the file carries them.
Fujifilm's image counter lives in MakerNote tag 0x1438. ExifTool's source notes that tag appearing with X-T1 firmware version 3 in 2014; the X-E1 was announced in September 2012. The full-size X-E1 files we checked simply do not contain the tag, and no tool can read a number that is not in the file.
Not from the files we have checked. ExifTool 13.59 returns no ImageCount for the full-size X-E1 RAF files in our release corpus. You can confirm it on your own file with: exiftool -a -G1 -ImageCount FILE.RAF. An empty result means the tag is absent.
Ask a Fujifilm authorised service centre whether they can read the body's counter during an inspection, and check the camera itself: shoot at several shutter speeds and look for uneven or partly dark frames, try every dial and button, check the EVF and rear screen, and inspect the sensor and lens mount. The number in the file name (DSCF1234) is a file-numbering counter, not a shutter count.
We have found no shutter durability rating published by Fujifilm for the X-E1. Figures quoted online for this body are estimates without a manufacturer source, so this page does not give one.
Yes. E-mail an unedited X-E1 RAF straight from the card to samples@shuttercount.app, ideally together with the count Fujifilm service reported for the same body. It helps us verify whether any X-E1 file carries a counter; it is not a promise that support will follow.