People are customizing what their cameras can do with the help of new tools. It could change things forever.
If you’ve looked away from camera communities for even a second, you may have missed the recent sea change: all of a sudden, it seems like everyone on Reddit and Instagram is running custom firmware on their cameras. Some examples are people showing off something they’ve made for private use, while others are publicly available, letting you install them on your camera after downloading a file or two from the internet.
The capabilities and ambition of the software varies wildly. Some people are using it to add some custom color modes onto their cameras, or port features from a manufacturer’s latest models onto older ones. Others are creating entirely new tools to give their cameras features the manufacturers never intended. Some, of course, are running Doom (a tale as old as time).
Hacked firmware for cameras has existed before, but it’s never been this widely distributed or contentious. Some subreddits, like r/SonyAlpha, have banned discussion of reverse engineered firmware outright, while others seem to have new posts about people customizing their cameras’ software every day. But where has it all come from, and what are the potential ramifications of this current explosion?
A (not so rich) history
Hacked firmware for cameras hasn’t exactly been prolific, but there have been some notable examples. One of the first major ones came out around 2006: the Canon Hack Development Kit or CHDK, designed to add new features to Canon PowerShot compacts. These ranged from relatively simple changes, such as an RGB histogram, to fundamental ones, such as the ability to shoot Raw, or use an aperture priority mode.

A few years later, after the release of the Canon EOS 5D Mark II, work began on Magic Lantern, which was designed to turn Canon’s DSLRs into even more capable video tools, though it eventually expanded to add stills features as well. Around the same time, the PTool hack for the Panasonic GH1 and, later, GH2, also expanded those cameras’ video capabilities.
While these hacks were impressive and useful to a lot of people, they were also only ever available for a select handful of cameras. And, until now, this kind of tinkering has been far less popular in the mirrorless age, likely due to some mixture of increased security around firmware and cameras generally shipping with the features that people previously had to add themselves.
AI inside
All that has changed now, with many of the latest cameras on the market having their firmware hacked in the past month or two. While previous modifications were generally add-ons – they augmented the cameras’ built-in firmware, running on top of it, rather than replacing it – that’s not universally true today. Some of the popular new tools are side-loaded, while others replace the camera’s stock firmware entirely.
You might not be surprised to hear that this current explosion in custom development is largely thanks to increasingly sophisticated AI tools, enabling people without extensive software development experience to “vibe code” their way through projects. While these have been around for a while, they’ve recently become quite good at what’s known as decompiling*: taking published software, or firmware files, and deriving and interpreting their source code, in a way that would take a human a lot of time, effort and expertise to do.
If you’re eating a cake, you probably have a reasonable idea of what’s in it
For those without a background in software development, imagine a cake (which, in this metaphor, is your camera’s firmware). If you’re eating it, you probably have a reasonable idea of what’s in it, but would struggle to come up with the exact recipe for it, even if you had a list of ingredients. There was once a very popular YouTube series based on exactly this premise.
Decompiling gets you that recipe which, importantly, lets you make changes to it. We’ll avoid stretching the metaphor further, but the point is that the latest tools give people much greater access to the software that runs on their cameras than ever before, while also greatly lowering the barrier to entry of then modifying it.
With great power comes great features

So what are people doing after hacking their camera’s firmware? Well… what aren’t they doing?
One very popular genre of hack is adding in features that the manufacturer supposedly “left out.” For example, people have been adding open gate recording to a variety of Sony, Nikon and BlackMagic cameras, anamorphic desqueeze preview to Red cinema cameras, a 65:24 “XPan” mode to the Panasonic S9, highlight-weighted metering to Fujifilm cameras and continuous autofocus and video to the original Hasselblad X2D. The latter notably lacked both those features at launch, and the hack has reportedly earned the ire of Hasselblad’s lawyers.
Some examples of these modifications are relatively fundamental, and are perhaps a bit awkward for camera companies. There’s work on porting many of the features from the OM System OM-1 Mark II to the previous-gen OM-1, something that OM System implied couldn’t be done when people accused it of releasing a firmware update as a new model of camera. By the same token, several people have modified the software on their OM System cameras to allow them to use the aperture rings on Panasonic lenses. The fact that they weren’t cross-compatible before has been a bit of an embarrassing state of affairs, given that interoperability was supposed to be a core feature of the Micro Four Thirds system.

Other projects go beyond adding features that already exist in a manufacturer’s ecosystem. One of the more extensive projects we’ve come across is Caduceus for the OM-3 and OM-5 Mark II. It adds a relatively advanced color editor for your out-of-camera JPEGs (which can be synced with a desktop app, if you don’t want to create looks on your camera itself), and adds several “film sim” presets.
That latter point is a common well for custom firmware developers to visit. We’ve seen people adding film-mimicking color modes to many, many cameras, including several Ricoh GR and Canon cameras (with the latter being a side-loaded modification built on top of Magic Lantern).
It’s hard to overstate just how varied and widespread these projects are, and how many new ones are popping up every day. These projects are global – we’ve seen repositories for them in English, Chinese, Korean and Japanese, though this is far from an exhaustive list – and the development is disparate, with people managing feature requests and feedback via Reddit, Instagram comments, Discord, Github, dedicated websites and more. And again, for every public project, there seems to be just as many people simply playing around with their own cameras, without any intent to release the software to the public.
Warranty void if installed?
A few of the latter developers have cited a common reason for keeping their software on their own machines: fear of repercussions from manufacturers. While there’s been a growing push for legislation to protect people who want to modify the software on devices they own, in the US, the Digital Millennium Copyright Act prohibits “circumventing technological protection measures (or TPMs) used by copyright owners to control access to their works.”
Assuming camera-makers have made an attempt to keep people’s hands off their firmware, this means that it’s not even legal to mess around with your camera’s firmware on your own, though obviously you’re much more likely to get caught if you then distribute your modifications, especially if you try to charge people for them, though currently that instinct doesn’t seem particularly widespread.

Even for those living in places not covered by the DMCA or similar laws, there are still reasons to treat this kind of modification with some caution. We spoke to a representative for a camera company to ask if installing firmware hacks could void your warranty, and their response wasn’t black and white. “If you’re within the warranty period, you may not be covered,” they say. They also pointed out that if you’re outside the warranty period and the firmware causes hardware damage, “it may no longer be possible to get the parts to repair your camera.”
Installing software made by people whose software engineering experience may be limited to coming up with AI prompts onto a device that’s not designed to run it is somewhat of a gamble with your camera’s life. “It should be obvious that this would be at your own risk,” says our contact. Even installing official firmware isn’t entirely risk-free.
While there are some modifications that don’t entirely overwrite the camera’s firmware, manufacturers typically don’t design the software on their cameras with the idea that people will mess with it. (There are a few exceptions: Camera Intelligence just announced a “Creative Sandbox” feature to tap into this explosion in experimentation, which provides a cordoned-off place in its OS to run your own software and tools.)
There are at least a few people online who have reported bricking their cameras by messing around with their own software, or with someone else’s projects. While it doesn’t seem to be incredibly widespread, it’s also unlikely that you’ll get much support from your camera manufacturer if software made by someone else breaks it.
The future of cameras?

As with many vibe-coded projects, it’s easy to look at how quickly some of this stuff has sprung up and decide that camera companies are doomed, or that they have to respond by picking up the pace at which they develop features. And indeed, it’s hard to look at things like Nikon’s months-long rollout of the ZR’s 2.0 firmware and not think that there’s room for improvement.
But it’s also worth keeping in mind that there’s a huge difference between creating software and creating a product. When a camera manufacturer introduces a new feature, the expectation is that it will work how they describe it. If it doesn’t, they’ll face serious reputational damage and community backlash. Likewise, if their software makes your camera unusable, it’s not unreasonable to expect them to fix it.
“The amount of effort that goes into validating firmware and making sure a change doesn’t have a knock-on effect elsewhere is why firmware development can seem to take so long,” says the spokesperson we talked to. “Because we have to be able to back that up with support.”
“We have to be able to back that up with support.”
While some of the people behind these projects have attempted to help those who ran into problems using software they published – or have shied away from publishing it at all to avoid having to support users – you’d be in a very gray area as to whether there’s any implied liability for resolving any issues. Also, depending on the level of AI-assistance, it’s always possible that the person behind the software may not even know how to fix a bug if their LLM of choice can’t figure it out. “The risks of damaging your camera should probably weigh on the people doing it,” says our contact.
None of this is meant to fear-monger about these projects, or to say that they’re flashes in the pan. Magic Lantern has stuck around for over a decade, so it’s obviously possible for these kinds of custom firmware projects to exist long-term. But getting an AI to code some software, and maintaining that software over years to patch bugs and maintain compatibility with future official firmware updates (some of which may explicitly try to block your code) are two very different things.
Regardless, there will almost certainly be those who do stick it out, and who manage to navigate the tricky legal waters. At the very least, it seems inevitable that this sudden wave of popularity will ensure that consumers are aware that hacked firmware is a thing that exists, and that is possible. As with many things related to AI, the future of camera software feels very up in the air, and it may hinge on how corporations respond to a disruption that’s based on the unauthorized use and modification of their software. But for photographers and videographers, it’s never been a better time to have a specific feature request… as long as you’re willing to take some risks to get that customization.
Additional reporting by Richard Butler.
* – Ironically, getting an AI tool to decompile something for you can be a hack in and of itself. Some of the companies that build them are trying to prevent them for being used to reverse engineer other software, due to concerns over IP infringement. It’s a funny line for them to draw, given that the models are based on every copyrighted work they could get their scanners on.


