Straight answer first: your EOS-1D Mark II N writes its actuation total into every CR2, but the browser tool on this site does not read it for this body. The value sits in the Canon MakerNote FileInfo block with its two 16-bit halves swapped, and this parser takes that field only from the big-endian files written by the original 1D and 1Ds. Drop a Mark II N file in and you get model, exposure data and capture dates — no count. ExifTool reads it in one command, and unlike most bodies of this age the rating to measure it against is a published Canon figure, not a guess.
Canon announced the EOS-1D Mark II N on 22 August 2005 and shipped it that September. It is not a new generation: it keeps the April 2004 Mark II's 8.2-megapixel APS-H CMOS sensor, DIGIC II processor and 8.5 fps burst, and spends its changes on everything around them. The 2.0-inch screen became a 2.5-inch, 230,000-dot panel with fifteen interface languages, Picture Style replaced the old processing parameters, the buffer grew from 40 to 48 full-resolution JPEGs, startup dropped from 0.3 to 0.2 seconds, and the dual CF + SD slots gained split RAW/JPEG recording — RAW to one card, JPEG to the other. Canon introduced it at an estimated $3,999, five hundred dollars below the Mark II's launch price.
It is the last of Canon's 200,000-cycle APS-H bodies before the 1D Mark III arrived in 2007 with a different metadata layout and a shutter-count field nobody can trust. There is no live view, no video mode and no electronic shutter on the Mark II N, which makes the actuation question unusually clean: every recorded frame is one mechanical cycle, so the counter and the wear track each other exactly.
| Specification | Canon EOS-1D Mark II N |
|---|---|
| Announced / marketed | 22 August 2005 · from September 2005 · est. $3,999 |
| Sensor | Approx. 8.20 MP effective APS-H CMOS (28.7 × 19.1 mm), DIGIC II |
| Mount | Canon EF (no EF-S) |
| Viewfinder | Eye-level pentaprism, approx. 100 % coverage, 0.72× |
| LCD | 2.5-inch TFT, approx. 230,000 dots, 15 interface languages |
| Autofocus | 45-point Area AF, working range EV 0–18 |
| Sensitivity | ISO 100–1600, expandable to 50 and 3200 from the menu |
| Shutter | Electronically-controlled focal-plane, 1/8000–30 s, X-sync 1/250 s |
| Burst | Approx. 8.5 fps · approx. 48 JPEG / 22 RAW frames |
| Live view / video / e-shutter | None — every frame is a mechanical actuation |
| Storage | CompactFlash (Type I/II) + SD, with split RAW/JPEG recording |
| RAW format | CR2 (12-bit), DCF 2.0 / Exif 2.21 — carries the shutter count, see below |
| Body / dimensions | 1,225 g body · 156 × 157.6 × 79.9 mm |
| Shutter durability | 200,000 exposures — stated by Canon, see Sources |
| Browser tool support | Model and EXIF yes · actuation count no |
Canon writes an in-file shutter count on almost nothing. Consumer bodies — every Rebel/xxxD, the 5D, 7D, 60D, 80D and their descendants — keep the counter in hardware and expose it only over USB; their files carry a file number and nothing more. The professional 1-series of the early 2000s is the exception, and the Mark II N is in it.
The value lives in the Canon MakerNote at tag 0x0093, the block ExifTool calls FileInfo, as its first entry. On the original EOS-1D and EOS-1Ds — which write big-endian TIFF-structured files — it is a plain 32-bit unsigned integer. On the 1D Mark II, 1D Mark II N and 1Ds Mark II, which write little-endian CR2, the same four bytes are stored with their two 16-bit halves swapped: ExifTool recovers the real number with ($val>>16)|(($val&0xffff)<<16), under a condition that matches exactly those 1Ds? Mark II model names.
0x0093 shutter count only from big-endian files, because on little-endian bodies that same tag's first word is a data length on consumer cameras — reading it blindly would print a plausible-looking wrong number for a 5D or an 80D. Rather than special-case the handful of 1-series models that do carry a real value there, the parser skips little-endian 0x0093 entirely. The 20 September 2026 full-corpus run confirms the consequence: on the EOS-1D, 1D Mark II N and 1Ds Mark II files in the release corpora, exiftool recovers a count and this tool reports none. That is a gap in this tool, not in your camera — and it is a deliberate one, chosen so that no body is ever shown a number that is not its own. If you have a Mark II N CR2 to spare, samples@shuttercount.app is where sample files for closing gaps like this go.
| Canon 1-series body | Where the count lives | Browser tool |
|---|---|---|
| EOS-1D / EOS-1Ds | MakerNote 0x0093 FileInfo[1], big-endian uint32 | ✗ Path exists, but never fired on a real file |
| EOS-1D Mark II / 1D Mark II N / 1Ds Mark II | MakerNote 0x0093 FileInfo[1], little-endian, 16-bit halves swapped | ✗ Not decoded |
| EOS-1D Mark III / 1Ds Mark III | CameraInfo 0x0d offset 0x176 — unreliable on these bodies | ✗ Deliberately withheld |
| EOS-1D Mark IV and later CR2 1-series | No usable in-file field for this tool | ✗ USB only |
| EOS R1 / R3 / R5 / R6 and the CR3 generation | CTMD metadata track, tag 0x000D, model-specific offset | ✓ Read in the browser |
The first row is worth reading carefully, because it is the one that sounds like an exception and is not: the big-endian branch is in the parser, but the full-corpus re-validation found it never fires on a real file from any 1D-family body either. On Canon, in practice, the browser tool reads a shutter count from the CR3 generation and from nothing older.
ExifTool is the free, open-source metadata reader that knows the word-swapped layout. It runs locally, reads the file and changes nothing.
The reply is a single line:
If nothing comes back, add -a -G1 to list every group ExifTool found — on a Mark II N file a MakerNotes group should be present and carry FileInfo. An empty result almost always means the file has been through an editor, or is a JPEG that was re-compressed. An out-of-camera JPEG from this body usually carries the same MakerNote, but the CR2 is the reliable choice.
If you have the camera in your hands rather than a file from a seller, the hardware counter is the better source, because it cannot have been edited at all:
gphoto2 --get-config /main/status/shuttercounter with the camera in PC connection mode.There is no menu item on the Mark II N that displays the count — Canon has never put one on an EOS body.
This is one of the few bodies on this site where the denominator is a real manufacturer number. Canon's own white paper for the EOS-1D Mark II N states that the shutter is “durability-tested to 200,000 exposures” and, in the reliability section, that it “is tested for 200,000 cycles”. So the percentages below are measured against a published specification rather than a class-norm estimate.
| Actuation count | Share of the 200,000 rating | Assessment |
|---|---|---|
| 0 – 20,000 | 0 – 10 % | Very low for a press body — verify it was not sitting unused for years |
| 20,000 – 80,000 | 10 – 40 % | Low to moderate — a well-kept second body |
| 80,000 – 150,000 | 40 – 75 % | Ordinary working life for this camera |
| 150,000 + | 75 %+ | Past three-quarters of the rating — price it as a body that may need the shutter unit |
Treat the rating as a tested median, not a cliff. Shutters fire well past 200,000 routinely, and some fail earlier; what the number buys you is a sense of how much of the designed life has been spent.
On a body now twenty years old, the count is rarely what decides the purchase. The things that end a Mark II N are usually elsewhere: the NP-E3 nickel-metal-hydride pack, which self-discharges and loses capacity with age and is no longer made; the mirror and shutter becoming sluggish after long storage; CF slot pins bent by a mis-inserted card; and sticky rubber on the grip. An 8.2-megapixel file and ISO 1600 as the practical ceiling are the other half of the honest picture — this is a camera bought for its handling, its viewfinder and its 8.5 fps, not for resolution.
One advantage over any modern body: with no electronic shutter and no video mode, the Mark II N's counter is the actuation count. On a current mirrorless camera most frames may never have touched the blades, and the number in the file answers a different question than the one you are asking.
Even without the count, dropping a Mark II N CR2 into the tool is worth doing when you are checking a listing — everything it reports is verifiable fact about the camera that made the file:
Everything runs in your browser; no file is uploaded. For the actuation total on this particular body, use the ExifTool command or the USB route above.
If you want a count verifiable from a single sample file without installing anything, the CR3 generation is where that works on Canon. The tool reads the CTMD metadata track, and the bodies below were confirmed against full release samples rather than inferred.
No — not for this body. The count is in the file, but this parser takes Canon's FileInfo shutter-count field only from the big-endian CR2 files written by the original 1D and 1Ds. The Mark II N writes little-endian CR2 with the value's two 16-bit halves swapped, and the parser skips that path rather than risk printing a wrong number on a consumer body that uses the same tag for something else. ExifTool reads the same file in one command.
200,000 exposures — and in this case that is a manufacturer figure rather than the usual community estimate. Canon's own white paper for the camera says the shutter “is still durability-tested to 200,000 exposures”, and Canon published the same 200,000-cycle rating for the preceding EOS-1D Mark II.
Yes. ExifTool handles the 1D Mark II, 1D Mark II N and 1Ds Mark II with one rule — same tag, same word-swapped layout. ExifTool does attach one caveat to that group: there are reports that the count changed on a 1Ds Mark II after loading a settings file onto the camera. Treat a wildly implausible reading on any of these three as worth a second sample rather than as fact.
No. The counter comes from the camera body, so formatting cannot touch it. What formatting and the file-numbering setting can restart is the DCF file number — worth knowing, because file numbers are routinely mistaken for actuation counts. A body writing IMG_0042.CR2 may have fired two hundred thousand frames.
Different reason, same honesty rule. The Mark III does have a CameraInfo field ExifTool labels ShutterCount, but ExifTool itself warns it “may be valid only for some 1DmkIII copies, even running the same firmware”, and our reference files show it stale, zero, or mirroring the file number. A number that is sometimes right is worse than no number when someone is pricing a camera on it, so this site withholds it.
Rarely, on economics alone. Canon's service support for the body has long ended, parts come from donor cameras, and a working Mark II N costs less than a shutter job would. If the camera is otherwise sound and you want it kept running, an independent repair shop is the realistic route — see shutter replacement cost for what the work generally runs.
Model, marketing date of September 2005 and the body specifications — sensor, shutter type and speeds, viewfinder, dimensions and weight: Canon’s own Camera Museum entry for the EOS-1D Mark II N. The 200,000-exposure shutter rating, the 22 August 2005 announcement, the $3,999 estimated price, the 48-frame JPEG / 22-frame RAW buffer, 45-point Area AF, ISO 100–1600 (expandable to 50 and 3200), the 0.2-second startup and split RAW/JPEG recording: Canon’s EOS-1D Mark II N white paper, “The New Professional Standard” — “its shutter is still durability-tested to 200,000 exposures” and “the shutter is tested for 200,000 cycles”. Shutter type, speed range and X-sync cross-checked against Canon’s EOS-1D Mark II N instruction manual (Canon download server); note that the manual’s specification pages do not quote a durability figure — the white paper is the source for it. The 200,000-cycle rating of the preceding body, for comparison: Canon’s Camera Museum entry for the EOS-1D Mark II (“shutter durability capable of withstanding 200,000 cycles”). Location and layout of the shutter-count field — MakerNote tag 0x0093 (FileInfo), first entry, the 1Ds? Mark II model condition and the ($val>>16)|(($val&0xffff)<<16) half-word swap, plus the 1Ds Mark II settings-file caveat and the 1D Mark III reliability warning: ExifTool’s Canon module, Canon.pm, and the published Canon tag names. Which paths this site’s parser decodes, and the full-corpus result that this body returns no count here while exiftool recovers one: the support matrix and validation report on the ShutterCount home page.