Microsoft has begun testing a new project file format for Paint that, for the first time, saves layers, ordering, and editing state in a single .paint file. The update, which is rolling out to Windows Insiders in the Canary and Dev channels, also introduces a per-tool opacity slider for the pencil and brush tools. Paint app version 11.2508.361.0 or higher includes these features, alongside support for exporting images in modern formats like AVIF and HEIF. The changes transform the classic inbox application from a single-session sketchpad into a lightweight, non-destructive editor suitable for multi-session creative work.
What actually changed
Microsoft is bundling three concrete enhancements in this Paint release, all of which were first detailed by Gagadget and corroborated by Windows-focused outlets.
The .paint project file
Paint now offers a File > Save as project command. Instead of flattening your image to a single-layer PNG or JPEG every time you close the app, you can now save an editable master that retains every layer, their stacking order, and your full session state. Reopen that .paint file later, and you pick up exactly where you left off.
This is the functional equivalent of what Adobe Photoshop’s .PSD or Paint.NET’s .pdn accomplish—except it’s built directly into a free, inbox Windows app that doesn’t require any installation or subscription. The workflow is straightforward: create a multilayer composition, hit Save as project, and close Paint. When you reopen the file, your layers and edits remain intact. When you need a shareable image, you can still export to conventional flat formats.
Importantly, Microsoft has not yet published a technical specification for the .paint container. It is unclear whether the file is an open ZIP-style bundle of assets and metadata or a proprietary binary blob. Until that documentation appears, .paint should be treated as a Paint-native working format with no guaranteed interoperability with third-party applications.
Per-tool opacity slider
A new opacity slider now sits next to the size control for the Pencil and Brush tools, letting you set stroke transparency anywhere from 0% (fully transparent) to 100% (fully opaque). This change, while small in UI surface area, dramatically improves the painting and shading workflow inside Paint. You can build tones with repeated low-opacity strokes, create soft overlays, and avoid the tedious workaround of creating temporary layers just to simulate transparency.
Independent hands-on reports confirm the slider’s real-time behavior and its placement to the left of the canvas. The feature is active for both standard brush strokes and pencil marks, and it works independently of the layer-level opacity setting that Paint already supports.
Modern export formats
Multiple sources note that Paint’s export dialog now includes support for modern image container formats beyond PNG and JPEG. You can export to AVIF and the HEIF/HEIC family, both of which deliver better compression efficiency and, in some cases, additional metadata like HDR support compared to legacy JPEG. Reporting from Gagadget and others highlights AVIF and HEIF/HEIC as available output options, though exact codec and container details remain imprecise. Until Microsoft releases definitive documentation, treat claims about specific codec wrappers with caution.
What it means for you
The practical impact of these updates breaks down differently depending on your role.
Everyday users gain the ability to work on a project across multiple sessions without losing editability. If you’re drawing a birthday card, annotating a screenshot that needs several revisions, or building a simple collage, you no longer need to export and re-import flattened images. The opacity slider also makes simple digital painting, shading, and glazing techniques accessible without extra tools.
Power users and hobbyists get a zero-cost, session-aware editor that can handle layered image creation for quick mockups, documentation, and light creative work. The .paint format acts as a native editable master, while the export options let you deliver final output in modern, space-efficient formats. However, Paint lacks adjustment layers, clipping masks, automation, and professional color management, so it won’t replace Photoshop, GIMP, or Krita for complex jobs.
IT administrators and managed environments should note several open questions. The proprietary .paint format may not be recognized by existing backup, data loss prevention (DLP), or eDiscovery systems. OneDrive sync behavior with large multilayer project files is untested and could lead to inefficient uploads or conflicts. Until Microsoft publishes a format specification or third-party tools add support, .paint files pose a long-term archival risk. Admins should pilot the update on test machines before wide deployment and update documentation to distinguish between editable working files (.paint) and archival exports (PNG, TIFF, JPEG).
How we got here
Paint’s evolution over the past two years has been measured and deliberate. The app, once frozen as a bare-bones raster editor, received layers and basic transparency in earlier Windows 11 updates. AI-powered features—generative fill, background removal, and Copilot integration—followed, gradually expanding Paint’s scope from simple annotation to lightweight image editing. The introduction of a persistent project format and per-tool opacity is the logical next step: it makes all prior additions practically usable across multiple editing sessions.
Microsoft’s strategy appears to be building a low-friction, zero-cost creative tool that covers the most common tasks Windows users actually perform—screenshot markup, quick sketches, social media images, and classroom assignments. The company is not trying to compete feature-for-feature with premium editors; instead, it’s prioritizing accessibility and deep OS integration.
Historically, Paint began as a licensed version of ZSoft’s PC Paintbrush bundled with early Windows, and it remained largely unchanged for decades. The current modernization effort signals a clear shift in how Microsoft views its inbox apps: as continuously updated services rather than static legacy components.
What to do now
If you’re a Windows Insider
- Join the Windows Insider Program and select the Canary or Dev channel.
- Update Windows 11 and the Paint app to version 11.2508.361.0 or newer.
- Create a multilayer composition and use File > Save as project to save a .paint file.
- Reopen the file later to confirm layers and state are preserved.
- Experiment with the brush and pencil opacity sliders to understand their behavior.
- Export a flattened PNG or JPEG to share when needed; optionally test AVIF/HEIF exports.
If you’re not an Insider
Wait for the stable release. Microsoft typically tests features in Canary and Dev channels for weeks before moving them to Beta and eventually to general availability. Attempting to sideload the updated Paint package carries stability risks and is not recommended for production machines.
General best practices
- Always save dual copies: Keep a .paint editable master and export a flattened PNG/JPEG for sharing and archival. This insulates you against format rot and compatibility gaps.
- Back up .paint files locally until the format’s longevity and OneDrive sync behavior are proven.
- Educate collaborators: If you share .paint files, ensure recipients understand that they need the updated Paint app to open them.
For IT administrators
- Pilot the update on a representative set of devices. Validate that backup, DLP, audit, and sync tools handle .paint files as expected.
- Update organizational policies to differentiate between working project files (.paint) and archival formats (PNG, TIFF).
- Review privacy and governance implications for any cloud-backed AI features that may interact with Paint, especially on managed devices.
Outlook
The single most important milestone to watch for is Microsoft publishing a formal .paint technical specification or developer documentation. That document will determine whether the format remains a Paint-only convenience or becomes a cross-tool asset that other editors can open and save. Should wide third-party support emerge, .paint could become a lightweight interchange format for layered images across the Windows ecosystem. In the shorter term, expect a gradual rollout from Canary/Dev to Beta and stable channels, and monitor whether Microsoft backports these features to older, supported Windows versions. Any announcements around PSD import/export or conversion pathways would further reduce interoperability friction and signal deeper professional aspirations.