Windows Paint gains layers, per-tool opacity, and .paint project files

Microsoft’s Paint has quietly shed its toy status and picked up features that turn it into a genuinely usable, session‑aware image editor: Windows Insiders are now seeing a new .paint project file that preserves layers and session state, a per‑tool opacity/ transparency slider for brushes and pencils, and expanded export options that include modern image container formats — changes documented in the Windows Insider flight for Paint (app version 11.2508.361.0) and corroborated by independent Windows coverage.

---

Background / Overview​

For decades, Paint was the archetypal simple raster editor bundled with Windows: light, fast, and intentionally limited. Over the last two years Microsoft has methodically rebuilt the app into a modern Windows 11 inbox application by adding layers, transparency, AI image tools (generative fill, background removal), and tighter Copilot integration. The latest Insider release formalizes two major workflow items that many creators asked for: the ability to save a multilayer editable project and finer per‑tool opacity control. Both features arrive as part of staged Insider channel testing in the Canary and Dev rings.
These are pragmatic, not revolutionary, changes: they do not attempt to replicate Photoshop’s professional toolset, but they materially reduce friction for students, hobbyists, documentation authors, and anyone who needs quick iterative editing without moving to paid software. The addition of a native project container converts Paint from a single‑session sketchpad into a tool that supports multi‑session, non‑destructive workflows.

---

What changed in Paint — the essentials​

Save as project: the new .paint file​

• Paint now offers a File > Save as project command that writes a single .paint file which preserves layers, ordering and session state so you can reopen and continue editing where you left off. This mirrors the fundamental convenience that native project formats like Photoshop’s .PSD or Paint.NET’s .pdn offer: one editable master document instead of a flatten/export juggling act.
• Practically, the workflow is simple: save your work to a .paint file, close Paint, and reopen the file later with layers and editability intact. You can still export flattened images (PNG, JPEG) for sharing. Independent coverage confirms Microsoft’s description of the Save as project behavior and the initial gated rollout to Insiders.

Important caveat: Microsoft has not yet published a formal technical specification for the .paint container. That leaves key questions — whether .paint is an open ZIP‑style container of assets and metadata or a proprietary binary blob, and whether it will support advanced layer metadata or third‑party interoperability — unanswered for now. Treat .paint as Paint‑native until Microsoft documents the format.

Opacity / transparency control for drawing tools​

• The Pencil and Brush tools now include a left‑of‑canvas opacity slider that sits alongside the size control. You can set stroke opacity anywhere from fully transparent to fully opaque and build tones with repeated low‑opacity passes — a core painting technique. This small UI change dramatically improves shading and glazing workflows within Paint.
• The opacity slider reduces the need for clumsy workarounds (temporary layers, constant layer opacity fiddling) for everyday sketching and annotations. Independent hands‑on reporting confirms the slider’s placement and real‑time behavior.

Modern export options (AVIF / HEIF / HEVC family)​

• Multiple reports note that Paint now supports modern image container formats alongside the usual PNG and JPEG exports, including AVIF and HEIF/HEIC‑family outputs. These formats offer better compression and modern features (such as HDR metadata in some cases) compared with legacy JPEG. Early coverage references AVIF and HEIF/HEIC capabilities in the updated app, but some details about codec wrappers (HEVC vs HEIF container naming) remain imprecise in public reporting; treat exact codec/container claims with caution until Microsoft publishes definitive documentation.

---

How this fits in the broader Paint evolution​

Microsoft’s strategy has been iterative and measured. Earlier updates added layers, basic transparency, improved brushes, and a set of AI features (Image Creator, generative erase, background removal). Those changes expanded Paint’s capabilities from single‑purpose annotation to genuine lightweight image editing. The introduction of a persistent project format is the natural, workflow‑level follow‑through: it makes all prior features practically usable across sessions.
The company appears to be positioning Paint as a low‑friction, zero‑cost alternative for many common creative tasks: quick mockups, classroom assignments, simple digital painting, screenshot annotation, and social‑media images. That positioning emphasizes accessibility and deep OS integration rather than competing feature‑by‑feature with premium editors.

---

Hands‑on implications: how users will benefit​

• Faster iteration: save an editable master (.paint) and come back to it without rebuilding layer stacks.
• Improved painting: per‑tool opacity lets you glaze and shade directly with the brush, producing richer results without extra layers.
• Simpler sharing: export flattened PNG/JPEG for recipients who do not use Paint, while sending the .paint master to collaborators who do.
• Better screenshots and annotations: semi‑transparent overlays and layer persistence make marking up captures less destructive and easier to refine.

Practical step‑by‑step (for Insiders):

• Join the Windows Insider Program and select the Canary or Dev channel.
• Update Windows 11 and the Paint app (confirm Paint is at v11.2508.361.0 or newer).
• Create a multilayer composition in Paint; use File > Save as project to write a .paint file to disk.
• Reopen the .paint file later to continue editing. Use the pencil/brush opacity slider to create layered shading.
• Export a flattened PNG/JPEG (or AVIF/HEIF where available) when you need a shareable image.

---

What Paint is not (and why that matters)​

It’s important to set realistic expectations. Paint is not attempting to become Photoshop nor does it offer the depth required for professional imaging pipelines.
Key professional features Paint does not (yet) provide:

• Advanced color management including CMYK workflows and ICC profile fine‑tuning.
• Adjustment layers, clipping masks, smart objects, and advanced non‑destructive filters.
• Scripting, automation, and the broad plugin ecosystems that professional tools support.
• Formalized interoperability guarantees (no published .paint spec or guaranteed PSD parity).

For professional or archival workflows, continue to rely on established editors (Photoshop, Affinity Photo, GIMP, Krita) and industry standard formats. Use .paint for editable masters within the Paint ecosystem, and export to TIFF/PNG/JPEG (or PSD where needed) for cross‑tool sharing and long‑term archives.

---

Interoperability, openness, and archival concerns​

The single biggest unknown affecting adoption is the technical openness of the .paint container. If Microsoft publishes a clear, documented spec (or if third‑party tools add support), .paint could become a convenient cross‑user container for Windows users. If it remains proprietary and undocumented, .paint will be convenient for Paint users but brittle for collaborative professional pipelines.
Potential risk scenarios for IT and content managers:

• Backup and DLP gaps: enterprise tools and backup systems may not recognize .paint as a recognized image type, complicating discovery, eDiscovery, and data loss prevention rules.
• OneDrive and sync behavior: large multilayer project files can interact differently with block‑level sync; untested behavior could cause inefficient uploads or sync conflicts.
• Long‑term archival: proprietary formats risk obsolescence; without documentation, future conversion or data recovery may be difficult.

Recommended conservative approach:

• Treat .paint as a Paint‑native working format only.
• Export flattened, widely supported images (PNG, TIFF, JPEG) for sharing and archival.
• Pilot the feature on test machines before wide deployment in managed environments.

---

Security, privacy and AI considerations​

Paint’s modernization came alongside expanded Copilot/AI features across Windows inbox apps. Some AI features are cloud‑backed, while Microsoft has indicated that certain on‑device AI capabilities are available on Copilot+ certified hardware. For Paint users:

• Verify where generative operations run (local vs cloud). On‑device generation reduces data leaving the machine; cloud features may have different privacy and retention characteristics.
• Be cautious when using pre‑release Insider builds in production environments. These builds can change behavior and may introduce instability.
• Check organisation policies for AI features — some generative tools require sign‑in, and behavior may vary by region and hardware certification.

---

Strengths and strategic value​

Why these changes matter in practice:

• Lowered friction: The ability to save an editable project removes the most common pain point for multi‑session, casual image work.
• Accessibility: Paint is free and built into Windows 11; adding project files and opacity extends real creative value to the broad Windows user base.
• Integrated AI roadmap: Paired with generative tools, Paint can serve as a one‑stop spot for quick edits, mockups, and image repairs without leaving the desktop.
• Educational value: For students and learners, Paint’s simplified UI plus non‑destructive editing creates a safer, easier ramp into digital art concepts.

These are significant wins for everyday users even if professionals will continue to prefer more capable, industry‑grade tools.

---

Limitations, open questions, and risks​

• Format specification: No published .paint spec today means interoperability and long‑term portability are unverified. Treat any claim that .paint will be PSD‑equivalent as speculative until Microsoft publishes format details or third‑party importers appear.
• Feature gating and rollout: The update is flighted to Windows Insiders (Canary/Dev). Not all devices will receive the change at once — hardware, region, and account signals can gate availability. Expect a staged roll‑out to Beta and Stable channels after testing.
• Enterprise and backup interaction: Until tested, admins should not assume existing DLP/backup systems will handle .paint files smoothly. Validate OneDrive sync behavior and backup appliances on test builds.
• Codec/format nuance: Reporting references AVIF and HEIF/HEIC exports; exact codec/container choices and licensing implications (for HEVC/HEIC) should be validated in Microsoft’s official release notes. Some public write‑ups conflate HEIF/HEIC with HEVC codec usage; treat such specifics as subject to confirmation.

---

Practical recommendations​

For everyday users:

• Try the feature on a non‑critical device by joining the Windows Insider program (Canary or Dev) if you are comfortable with preview builds.
• Save important work in two places: a .paint editable master and an exported PNG/JPEG for sharing and archival.
• Keep local backups of .paint files until interoperability is proven.

For educators and classrooms:

• Use .paint to let students submit editable projects, but require flattened exports for final grading to avoid long‑term format issues.
• Teach students to export both editable and flattened copies for continuity.

For IT admins:

• Pilot the Paint update on representative devices and validate backup, DLP and OneDrive sync behavior.
• Update policy and training materials to clarify what constitutes an archival format versus an editable project file.
• Evaluate privacy and AI governance implications for Copilot features on managed devices.

---

What to watch next​

• Microsoft publishing a formal .paint technical specification or developer documentation — this will determine long‑term portability and third‑party tool support.
• Any announced PSD import/export or conversion pathways that reduce interoperability friction.
• Broader rollout timelines from Canary/Dev into Beta and Stable Windows releases, and whether Microsoft backports the feature to older supported Windows versions.

---

Conclusion​

The recent Paint update marks a practical, user‑focused evolution that fixes long‑standing workflow friction: editable .paint project files and a per‑tool opacity slider convert Paint from a single‑session doodle tool into a capable, session‑aware image editor for everyday tasks. These changes matter because they make real the promise of non‑destructive, iterative editing in the most widely available Windows graphic utility — without charging a subscription. At the same time, crucial technical and governance details remain unverified: Microsoft has not yet published the .paint file specification, long‑term interoperability is unclear, and exact codec/container behavior (AVIF vs HEIF/HEVC nuance) needs firm documentation.
For now, the pragmatic path is straightforward: Insiders and curious users should test the new features, creators should keep both .paint masters and flattened exports, and IT administrators should pilot before wide adoption. If Microsoft opens the .paint format or provides robust import/export guarantees, these updates could shift how millions of Windows users create and exchange layered images. Until then, Paint’s renaissance is an important and welcome improvement — a significant upgrade to better Paint rather than a full replacement for professional editors.

---

Source: Gagadget.com Microsoft Paint: The next level of graphic editing for Windows 11