Microsoft Paint Update Adds .paint Projects and On Canvas Opacity for Windows Insiders

Microsoft's latest Paint update introduces editable project files and on‑canvas opacity controls, a pair of small but pivotal features that sharply reduce the friction between casual sketches and multi‑session image projects — and bring the classic Windows app closer to being a viable, zero‑cost alternative for many everyday Photoshop tasks.

Background​

Microsoft has been steadily rebuilding Paint from a single‑session doodle tool into a more capable creative surface over the past few years. The app already gained support for layers and transparency, plus a suite of AI‑assisted features such as background removal, generative erase, and in‑app image generation, all designed to make quick image edits easier for the broad Windows user base.
The update currently being flighted to Windows Insiders in the Canary and Dev channels formalizes two workflow features long requested by creators: a native project container written with a .paint extension (accessible via File > Save as project) and a per‑tool opacity slider for the Pencil and Brush tools that appears on the canvas UI. Microsoft documents the rollout and associates it with Paint app version 11.2508.361.0 in its Insider announcement.

---

What changed: the two headline features​

.paint — a native, editable project file​

• Paint now offers a Save as project command that writes a single file with the .paint extension.
• The .paint file preserves the document’s layers, layer order, transparency, and editing state, allowing the user to reopen a project and pick up exactly where they left off.
• This behavior mirrors the fundamental convenience offered by professional editors (for example, Photoshop's .PSD or Paint.NET's .pdn), and addresses a long‑standing workflow gap in Paint: the need to export multiple layer assets or keep messy intermediate files just to preserve an ongoing composition.

Why this matters: a working, non‑destructive master file is the backbone of iterative creative workflows. Students, hobbyists, casual artists and documentation teams who previously had to rebuild layer structures or save multiple intermediary exports can now maintain a single editable master document — the .paint file — while exporting flattened PNG/JPEG copies for sharing.

Opacity slider — per‑tool transparency control​

• The Pencil and Brush tools gain an opacity slider visible on the canvas (left side) when selecting those tools.
• This slider lets users apply semi‑transparent strokes per stroke, enabling glazing, soft shading, and buildable tones without resorting to layer‑opacity workarounds.
• The change is deceptively powerful: semi‑transparent strokes and repeated low‑opacity passes are foundational painting techniques that significantly upgrade Paint's feel for sketching and illustration.

Practical effect: combined with layers, the opacity slider means Paint can now handle shading, subtle compositing and annotation workflows far more naturally, making it far more useful for quick creative tasks and polishing images prior to export.

---

Verified timeline and channels​

Microsoft announced the project file and opacity slider in a Windows Insider post dated September 17, 2025, explicitly noting the features are rolling out to Windows Insiders in the Canary and Dev channels and identifying the Paint app version as 11.2508.361.0. The features are staged and gated by Microsoft’s flighting controls; they are not yet guaranteed to appear in Beta or stable release builds until broader testing completes.
Independent tech outlets also reported on the Windows Insider announcement and validated the high‑level claims, confirming that the .paint container and on‑canvas opacity slider are part of the latest Insider flight.

---

Critical analysis: how close is Paint to Photoshop?​

Paint's new features are meaningful, but equating Paint with Photoshop requires nuance. The update narrows the gap in everyday workflow convenience, but does not erase the deeper technical and ecosystem differences that keep professional workflows anchored to Photoshop.

Strengths — where Paint now shines​

• Zero cost and ubiquity. Paint ships with Windows and updates via Store/inbox channels, making advanced editing features widely accessible without subscription barriers. This continues to be Paint’s strongest advantage.
• Lower learning curve. For quick edits, mockups, screenshot annotations, classroom use and casual digital painting, Paint's simplified UI remains far friendlier than Photoshop’s complexity.
• Faster single‑app loop. Project files plus on‑canvas opacity make the single‑app creative loop faster: generate or edit with AI tools (background removal, generative fill), preserve your layered master in a .paint file, then export flattened assets for sharing. That speed is valuable for social creators and documentation workflows.
• Integrated AI helpers. Recent additions such as Cocreator/Generative Erase enhance Paint's capabilities for fast fixes that previously required third‑party tools. Those features compound the value of the new project workflow by making edits quick to perform and easy to preserve.

Weaknesses — where Paint still falls short​

• Feature depth. Photoshop remains the industry standard because of advanced capabilities that Paint does not offer: CMYK color management for print, advanced layer types (adjustment layers, layer masks, smart objects), complex blending modes, nondestructive filters, color profiles, and precision retouching tools.
• Ecosystem and extensibility. Photoshop's plugin marketplace, scriptability, professional color workflows and enterprise integrations are orders of magnitude larger than anything Paint currently supports.
• Interoperability uncertainty. Microsoft has not published a technical specification for the .paint container yet. There is no official guarantee of PSD import/export parity or a documented container format for .paint, which means interoperability across mixed toolchains and long‑term archival use are open questions. Until Microsoft publishes a spec or third‑party tools add support, treat .paint as a Paint‑native working file rather than an exchange format.
• Enterprise and governance concerns. New file types can complicate backup, DLP, eDiscovery and archival policies. IT administrators should test .paint file behaviors in their environments before endorsing them for production workflows.

In short: Paint now covers many of the daily tasks people reach for Photoshop for — cropping, basic retouching, background removal, quick composites, sketches and social‑media graphics — but the professional edge in high‑fidelity print, color‑critical work and scripted automation remains firmly with Photoshop.

---

Technical verification and outstanding unknowns​

The following statements are confirmed from Microsoft’s Insider communications and independent reporting:

• Microsoft added a Save as project command that writes .paint files to disk as a way to store layered, editable work.
• Paint’s Pencil and Brush tools now have an on‑canvas opacity slider enabling per‑stroke transparency control.
• The update is associated with Paint app version 11.2508.361.0 and is being staged to Canary and Dev channel Insiders.

Important caveats and open technical items:

• Microsoft has not yet published a formal .paint file specification. The internal file structure (for example whether it is a documented ZIP container, what metadata it stores, whether it embeds per‑layer metadata beyond pixel rasters) is presently unverified. Any claims about cross‑app compatibility or round‑trip fidelity with PSD are therefore unverified and should be treated with caution.
• There is no explicit promise of PSD parity or guaranteed interchange. Collaborative professional workflows that require exchanging layered, editable documents across different apps should continue to use established exchange formats until Microsoft publishes official interoperability guidance.
• Enterprise implications such as indexing, backup size characteristics, and how .paint files interact with DLP or eDiscovery systems remain to be documented and tested. Administrators should validate in controlled environments prior to production deployment.

---

Practical workflows and examples​

Everyday creator workflow (fast loop)​

• Open Paint and create base layers (background, midtones, linework).
• Use the Pencil/Brush with the new opacity slider to build shading and texture without creating extra layers.
• Use AI tools (background removal, generative fill) to quickly refine elements.
• Save the working file using File > Save as project (.paint).
• Export flattened assets (PNG/JPEG/AVIF/HEIC) for sharing or upload.

This simple loop keeps the working master editable while providing shareable exports — a workflow that previously required juggling multiple layer exports or non‑native workarounds.

Classroom and handoff workflow​

• Students or collaborators can hand off a .paint file that preserves layer order and current edit context, allowing another user to open the same file and continue editing.
• For classroom assignments or iterative group projects this reduces file‑management overhead and keeps a single canonical working file.

When to flatten before sharing​

• If the recipient is using Photoshop or a different editor, export a flattened PNG or JPEG for compatibility unless both parties confirm .paint support.
• For print or color‑critical workflows, export with appropriate color profiles from tools that support CMYK and professional color management. Paint’s current export options remain less suitable for high‑end print work.

---

Security, governance and IT recommendations​

• Pilot the new Paint build on non‑production machines in Canary/Dev before enabling it in broader environments; Insider channel builds can be unstable.
• Validate how .paint files are handled by your backup, DLP and eDiscovery tools. Some enterprise systems may not recognize new file extensions without policy updates.
• Require exported, standard formats (PNG/JPEG/TIFF) for records retention or circulation to external partners who may not support .paint files.
• Monitor Microsoft’s documentation and the Windows Insider Blog for updates including whether Microsoft publishes a .paint file specification or interoperability guidance.

---

Where this fits in the editing landscape​

Paint’s evolution positions it between lightweight editors (such as Paint.NET and Krita for hobbyists) and subscription‑grade professional tools (Photoshop). The addition of .paint projects and per‑tool opacity makes Paint far more competitive for:

• Quick mockups and social graphics
• Annotated screenshots and documentation assets
• Classroom assignments and student projects
• Casual digital painting and sketching

It remains less suited for:

• High‑end retouching and print workflows
• Color‑managed production pipelines (CMYK workflows)
• Plugin‑driven pro workflows and scripted automation

Compare and contrast in short:

• Paint (updated): Free, integrated, now supports persistent project files, per‑tool opacity and AI helpers. Great for speed and accessibility.
• Paint.NET / Krita: More advanced raster tools for hobbyists and illustrators, with communities and plugin support. Often stronger for painting workflows than Paint historically has been.
• Photoshop: Industry standards for professional retouching, print, advanced compositing, and production pipeline integrations.

---

Risks and what to watch next​

• Interoperability signals. Watch for an official .paint format spec or PSD import/export features; those would be the clearest indications Microsoft intends Paint to act as a cross‑app contender rather than a Paint‑native working format.
• Community tooling. If open‑source libraries or third‑party toolchains begin reading/writing .paint files, that will quickly increase practical interoperability and enterprise confidence.
• Rollout timing. Because the feature is staged to Canary/Dev, broad availability in stable Windows 11 may still be weeks (or longer) away; follow the Windows Insider Blog for official timing.
• Enterprise behavior. Confirm how .paint interacts with corporate file servers, OneDrive block‑level sync, and backup indexing to avoid surprises in storage overhead or retention policies.

---

Conclusion​

The addition of .paint project files and an on‑canvas opacity slider represents a practical and user‑centered evolution of Microsoft Paint. These two features address long‑standing workflow friction by letting users preserve layered, editable masters and paint with nuanced, semi‑transparent strokes. For millions of Windows users these small changes dramatically increase Paint's utility for everyday creative tasks and make it a credible, zero‑cost alternative for many use cases that previously nudged users toward heavier editors.
That said, Paint remains focused on accessibility and speed rather than professional depth. Without a published .paint specification, PSD parity guarantees, or the advanced color and scripting features professionals require, Paint should be viewed as a powerful companion and first‑pass editor — not a wholesale replacement for Photoshop in production environments. IT teams, educators and creators should pilot the new Insider builds, validate governance impacts, and continue to export final assets to stable, widely supported formats for collaboration and archival purposes.

---

---

Source: BGR This Upcoming Paint Feature Brings The Windows App One Step Closer To Being A Proper Photoshop Alternative - BGR