Adobe has quietly turned its Camera app into something closer to a pocket studio. With the introduction of Project Indigo, the company is adding an AI-driven background removal capability that works on photos you snap in the app—meaning the “edit” step can happen before you’ve even finished reviewing the shot. For users who regularly post portraits, product images, or social content, this is a meaningful shift: instead of treating background cleanup as a separate workflow, Adobe is trying to make it part of the capture moment.
Project Indigo’s core promise is straightforward: remove backgrounds quickly and consistently across a wide range of scenes. But the real story is less about the feature itself and more about what it signals for how camera apps are evolving. The modern smartphone camera already does computational photography—HDR stacking, noise reduction, portrait depth mapping, and scene-aware enhancements. What Adobe is now pushing is a different kind of computation: semantic separation. In other words, the app isn’t just improving pixels; it’s interpreting the image enough to decide what belongs to the subject and what should be treated as background.
That distinction matters because background removal is one of the most time-consuming tasks in everyday editing. Even when tools are “one click,” they often require follow-up corrections: refining edges around hair, dealing with semi-transparent objects, correcting halos, or reworking areas where the subject blends into similarly colored backgrounds. Adobe’s pitch with Project Indigo is that it’s designed to handle a broad set of backgrounds, reducing the amount of manual cleanup needed after the fact. If it performs as intended, it could compress a workflow that used to take minutes—or longer—into something that feels almost instantaneous.
What makes this particularly interesting is the context: Adobe is not positioning Project Indigo as a replacement for full-featured editing suites like Photoshop. Instead, it’s aiming at the gap between “capture” and “edit,” where most casual creators live. People don’t open Photoshop for every post. They want results that look good enough to publish, fast enough to keep up with their pace, and simple enough that they don’t have to learn advanced masking techniques. By bringing background removal into the camera experience, Adobe is effectively moving a piece of professional-grade capability into a consumer-friendly flow.
The “in-camera” angle is also a subtle but important design choice. Background removal is computationally heavy, especially when you want clean edges and reliable segmentation across varied lighting conditions. Doing it at capture time suggests Adobe has optimized the underlying pipeline—whether through on-device processing, efficient model execution, or a hybrid approach that balances speed and quality. The user-facing outcome is what matters: you take a photo, and the app can immediately separate the subject from the background without forcing you to export the image to another tool first.
This is where Project Indigo starts to feel like more than a single feature. Background removal is a gateway capability. Once you can reliably isolate a subject, you unlock a chain of downstream possibilities: swapping backgrounds, placing subjects into new environments, creating consistent cutouts for templates, generating assets for marketing posts, and even preparing images for compositing workflows. Many creators already do these things, but they typically rely on external apps or desktop software. Adobe’s move suggests it wants to make isolation the default starting point—something the app can do automatically so users can spend their time on creative decisions rather than technical cleanup.
There’s also a broader trend behind this. AI image tools have been racing toward “automation,” but automation only becomes truly valuable when it’s dependable. A background removal tool that works perfectly on one type of photo but fails on another can be more frustrating than helpful. Adobe’s emphasis on removing “all kinds of backgrounds” is essentially an attempt to address that reliability problem. The more varied the backgrounds it can handle—busy indoor scenes, outdoor foliage, patterned walls, mixed lighting—the more likely users will trust it enough to use it routinely.
And trust is the real battleground. In editing, users don’t just want a tool that can do something; they want a tool that reduces uncertainty. When you’re posting frequently, you can’t afford to discover after the fact that your subject edges look unnatural or that the segmentation missed key details. If Project Indigo delivers consistent results across common scenarios, it could become a default behavior rather than a special effect.
Another layer to consider is how background removal changes the way people think about photography. Traditionally, photographers compose with the final image in mind. But when the background can be removed instantly, composition becomes more flexible. You can shoot with less concern about cluttered environments, knowing the subject can be separated later. That doesn’t mean composition stops mattering—it still affects lighting, subject framing, and overall quality—but it shifts some of the burden away from the background and onto the subject itself.
For creators, this can be liberating. For example, someone filming a product for an online store might not have access to a perfect studio setup. If the app can isolate the product reliably, the creator can focus on product placement and lighting rather than spending time building a clean backdrop. Similarly, portrait shooters might use background removal to create consistent looks across different locations, turning spontaneous shoots into usable assets for social media or campaigns.
Adobe’s choice of Project Indigo as the name also hints at a philosophy: the company is leaning into AI as a creative assistant rather than a purely technical tool. Indigo evokes something like a spectrum—an in-between space where different elements can be transformed. While the feature described here is background removal, the underlying direction is clear: Adobe wants its camera experience to understand images semantically and help users manipulate them creatively.
The mention that the tool is designed to remove a wide range of backgrounds is important because background removal isn’t one problem—it’s many. Hair is one of the hardest cases. Motion blur is another. Low contrast between subject and background can break segmentation. Transparent objects—glassware, plastic packaging, reflective surfaces—introduce ambiguity. Shadows complicate everything because shadows can either be treated as part of the subject or as part of the background depending on the desired aesthetic. A robust system needs to make reasonable decisions across these edge cases, and then do so quickly enough to feel seamless.
If Project Indigo is truly built to handle “all kinds” of backgrounds, it likely incorporates strategies beyond basic segmentation. Modern AI approaches often combine multiple signals: object detection, instance segmentation, edge refinement, and sometimes temporal consistency if the app processes sequences. Even if the user only sees a single photo result, the system may be using sophisticated internal steps to improve boundary quality and reduce artifacts like jagged edges or color bleeding.
There’s also the question of how the app handles output. Background removal can mean different things: a transparent PNG-like cutout, a mask that can be edited later, or a background replaced with a solid color or blur. The most useful approach depends on the user’s next step. If Adobe is integrating this into the camera app, it likely aims to produce an immediate, usable result—something that can be shared right away or further edited within the same ecosystem. That matters because the value of background removal increases when it’s not a dead-end action. Users want to go from isolation to creativity without friction.
This is where Adobe’s ecosystem advantage comes into play. Adobe has long been strong in bridging workflows across devices and software. If Project Indigo is part of a broader strategy, it may eventually connect to other Adobe tools—either directly or through export formats that preserve masks and editability. Even if today’s feature is focused on background removal, the long-term goal could be to make AI-generated masks and selections portable across Adobe’s suite, allowing users to refine results in more advanced editors when they want to.
From a user perspective, the biggest benefit is time. Background removal is one of those tasks that people avoid not because it’s impossible, but because it’s tedious. It interrupts the creative flow. You take a photo, you like it, and then you spend time cleaning edges, adjusting selection boundaries, and fixing mistakes. If Project Indigo reduces that effort significantly, it changes the emotional experience of editing. Instead of “I hope this looks good after I fix it,” it becomes “I can get a publishable result quickly.”
But there’s also a creative implication: faster editing can lead to more experimentation. When the barrier to making a cutout is low, users are more likely to try background swaps, composite ideas, and stylized layouts. That can increase the volume of content and the variety of styles people attempt. In a world where social feeds reward novelty and consistency, tools that make experimentation easier can have outsized impact.
At the same time, it’s worth acknowledging that AI background removal is not magic. Even the best systems can struggle with certain scenarios. Users will still encounter photos where the subject merges with the background, where fine details are lost, or where the cutout looks slightly unnatural. The difference is whether those failures are rare enough—and the successes frequent enough—that users stop thinking about the tool and start thinking about the creative outcome.
Adobe’s framing suggests it wants to reach that threshold. The company is positioning Project Indigo as a capability that removes backgrounds “directly on photos you snap,” which implies a focus on immediacy and usability. That’s a bet that the average user will value speed and convenience over perfect edge fidelity. For many use cases—social posts, quick product listings, casual portraits—that tradeoff can be acceptable, especially if the results are consistently good.
There’s also a subtle competitive angle. Many camera and photo apps have added AI features, but background removal is a particularly strategic one because it’s foundational. It’s not just a filter; it’s a transformation that enables other transformations. If Adobe can make background removal a reliable default, it can become the “first step” in a larger set of AI-assisted edits. That could include style changes, compositing, and potentially automated critique or enhancement suggestions—features that align with the broader idea of AI helping users improve their photos.
In fact, the way Adobe is rolling out Project Indigo fits into a larger pattern: AI features are increasingly being integrated into the capture and review loop, not