Notepad Adds Image Embedding to Inline Markdown (Preview)

Microsoft is testing the ability to insert and render images inside Notepad — a move that would extend the app’s Markdown-based formatting into inline visual content and deepen the transformation of a once-minimal text editor into a richer note-taking and documentation tool.

Background​

Notepad’s identity has shifted markedly over the past 18 months. Once a deliberately minimal, plain-text utility for fast edits and config changes, Notepad received a series of feature additions in 2025 that changed how many people use it: Markdown rendering, a formatting toolbar (bold, italic, lists, headings), table support, and an AI “Write” tool tied to Microsoft’s Copilot services. Microsoft began rolling those capabilities to Windows Insiders in mid-2025 and has continued to iterate them in preview channels.
That evolution followed Microsoft’s formal deprecation and removal of WordPad from Windows 11 24H2, leaving Notepad as the closest built-in app for any sort of rich-text-light workflows. For users who previously relied on WordPad for basic rich-text editing, Microsoft’s strategy effectively funnels them into the Notepad+Markdown model or into installing third‑party document software.
At the same time, Microsoft has added a first-run “What’s New” experience to Notepad so the company can highlight new features directly in the app. Screenshots and Insider build previews have begun showing an “Image” icon in that interface, which is the clearest sign to date that image embedding is actively under development. Microsoft reportedly confirms internal testing of the feature.

---

What’s being tested: image insertion in Notepad​

What we know so far​

• Preview builds and screenshots seen in the Windows Insider ecosystem show an Image toolbar button in Notepad’s “What’s New” and formatting bar. The control is sometimes visible but not yet functional in the earliest previews.
• Reporting based on unnamed internal sources indicates engineers found no significant performance impact from enabling images during tests, and Microsoft intends to expose a settings toggle so users can preserve a classic plain-text experience if they prefer. Those performance claims are currently Microsoft’s internal assessment relayed by outlets; they are credible but not independently verified outside of Microsoft testing.
• The image feature is being developed as part of Notepad’s Markdown support: Notepad will likely render images inline in its formatted (rendered Markdown) view while keeping a raw Markdown view accessible (the underlying file would still be text/Markdown). The exact syntax and storage model — whether images are referenced by URL or path, embedded as data URIs, or wrapped in some container — is not yet documented publicly.

What Microsoft has said (and what it hasn’t)​

Microsoft has acknowledged image support is being tested in Insider builds and says the feature can be disabled in settings, but the company has not published a detailed technical design or developer-facing documentation describing how Notepad will fetch, cache, sanitize, or persist images. Until Microsoft publishes formal release notes or a technical blog post, critical implementation details remain unverified. Treat public performance and security claims as early engineering statements that require confirmation at release.

---

How image support might work — implementation scenarios​

Notepad’s image support will be tightly coupled with Markdown rendering, so the implementation most likely follows patterns already established in Markdown ecosystems. The main approaches Microsoft could choose include:

• Reference-based rendering: the Markdown contains an image URL or local file path (e.g.,
  
  ,
  
  ). This keeps files lightweight but requires Notepad to handle remote fetches, local path resolution, and permission rules.
• Embedded data URIs: the image data is base64-encoded and stored inline in the Markdown. This guarantees portability but bloats text files and could have performance/memory trade-offs on large images.
• A sidecar or container format: Notepad could adopt a container approach (not unlike simplified app-packaging) where a text file and its media are kept together. That would preserve file cleanliness but break compatibility with standard .md workflows unless export/import rules are provided.
• Hybrid UX: show inline images in the formatted view but store only local references or URLs in the raw Markdown, with a user setting to determine whether images are transient (cached) or persisted. This approach balances rendering with file size and preserves plain-text integrity for users who want it.

All of these designs carry practical trade-offs that influence interoperability, file portability, security, and disk/network overhead. No public documentation yet clarifies which direction Microsoft will take, so the community can only infer likely behavior from the presence of the UI control and related Markdown updates.

---

Why Microsoft might add images to Notepad (the case for it)​

Better README, documentation, and note-taking workflows​

For developers and technical authors who use Markdown for README files, issue templates, and quick docs, inline images make certain tasks much easier: screenshots, architecture diagrams, annotated visuals, and embedded reference images are often a faster way to communicate than extended prose. Turning Notepad into a convenient, default Markdown editor with image support reduces friction for small documentation tasks that previously required heavier tools.

Modernizing a legacy tool to stay relevant​

Microsoft has demonstrated a product strategy of modernizing built-in utilities rather than letting them languish. By expanding Notepad’s capabilities — and connecting those capabilities to Copilot and Microsoft accounts for AI features — the company can present Windows as a richer out-of-the-box experience for users who expect modern editing conveniences. The move also fills the vacuum left by WordPad’s removal.

A single, discoverable entry point for lightweight rich documents​

Not everyone wants to install a new editor for occasional formatting needs. If Notepad can handle Markdown, tables, and images with minimal friction, the app becomes a practical compromise for users who need more than plain text but less than a full office suite. An integrated "What's New" and visible toolbar can surface these capabilities to users who might otherwise remain unaware.

---

The downsides and real risks​

Security: interactive Markdown already introduced a high-risk vector​

Notepad’s Markdown support has already expanded the app’s interactivity — and with interactivity comes attack surface. Microsoft patched a remote code execution vulnerability tied to Markdown handling that could allow attackers to execute commands via unverified protocols if a user clicked a crafted link inside a Markdown file. The vulnerability, tracked publicly, prompted an urgent patch in February 2026. That incident is a clear reminder: adding more interactive features (images that can be remote-loaded or clickable) increases the hazard profile of what was once a purely local, inert text file editor.

Network activity and privacy concerns​

If Notepad chooses to support remote image URLs — even for convenience — opening a Markdown file could silently cause network requests to external hosts. That behavior raises privacy, telemetry, and exfiltration concerns in corporate environments where offline, auditable workflows are required. Enterprises will want explicit settings to block remote fetches, and users will want clarity on whether images are fetched automatically or only after consent. Microsoft’s stated toggle for disabling the feature may help, but the default behavior at scale matters enormously.

File bloat, compatibility, and portability​

Embedding images as data URIs makes Markdown files large and less friendly for version control systems (git diffs become unwieldy). Conversely, referencing local file paths can break when files move between machines, or when sharing via email. Without clear export/import paths and compatibility with mainstream Markdown tools, the Notepad image experience risks introducing friction rather than removing it. Developers and authors depend on interoperable text formats; any proprietary container approach would be controversial unless it’s opt‑in.

Stability and feature creep​

Longtime Notepad fans complain that an app prized for speed and reliability is being used as a showcase for AI and formatting features. Each additional capability increases the code surface, which can lead to regressions, memory usage spikes, and new bugs. Notepad’s role as a small, dependable utility is at odds with the product management goal of turning it into a richer writing workspace. Community backlash is already visible in comment threads and tech coverage.

Supply chain and update security lessons​

The wider ecosystem offers cautionary tales: Notepad++ and other popular editors have been targeted via update infrastructure attacks in recent years, and attackers have exploited update mechanics to distribute trojanized installers. Any feature that increases reliance on automatic updates, remote asset fetching, or bundled online services merits additional scrutiny and hardened update verification. Microsoft should apply strict signature checks, certificate pinning, and telemetry safeguards where appropriate.

---

Community reaction and the broader debate​

Critics frame the Notepad changes as symptomatic of what they see as a trend in Windows: core apps morph into demonstrators for AI and online features. For users who want a small, offline utility, Notepad’s expansion feels like feature creep. Supporters argue that built-in apps should evolve to reflect modern workflows. Both views have merit: modernization improves convenience for many, but removing lightweight fallbacks or obscuring “plain-text” defaults creates friction for power users and administrative environments. The debate is not new, but the stakes are higher now that Notepad handles formatting, images, and network-aware content.

---

What to watch for — unanswered technical questions​

There are a number of key details Microsoft needs to publish before the community can form a fully informed opinion:

• Will Notepad embed images directly in the Markdown file, or will it reference them? The portability and safety implications are very different in each case. Unverified at present.
• If Notepad fetches remote images, will it block mixed-content, unverified protocols, or use safe fetch sandboxing that prevents executable payloads from being invoked? Given the recent Markdown-linked RCE, the implementation needs careful protocol whitelisting and sanitization. Unverified at present.
• How will Notepad handle large or animated images, and what limits will apply to cached content? Memory and performance constraints are non-trivial for an app historically optimized for tiny files. Unverified at present.
• Will Copilot or Microsoft account sign-in be required to use the feature, or is it fully local? For other Notepad AI features, Microsoft required Microsoft account sign-in for certain flows; clarification is needed here for privacy-conscious users and enterprise admins.

Until Microsoft publishes developer documentation or a security whitepaper for the feature, these points remain open and should be considered when evaluating adoption.

---

Practical guidance for users and administrators​

If you use Windows 11 and care about safety, privacy, or stability, here are pragmatic steps to protect yourself while the image feature is tested and rolled out:

• Keep Notepad and Windows updated. Microsoft already patched a Markdown-related RCE; running the latest updates reduces your exposure to known vulnerabilities.
• If you prefer a pure plaintext experience, turn off the new formatting/Markdown features in Notepad’s settings once an image option appears. Microsoft reportedly plans a toggle to preserve classic behavior; enable it to avoid rendered content and remote fetches. Check settings when the feature ships.
• Don’t open untrusted .md files or click links inside Markdown files in Notepad. Treat Markdown files with the same suspicion you’d apply to documents containing hyperlinks until you know how Notepad resolves and sanitizes them.
• For serious documentation projects, continue using established Markdown tools (VS Code, Obsidian, or specialized documentation platforms) that provide explicit controls for image storage and source control compatibility. These tools typically give you more transparency about local vs. remote assets.
• Enterprise admins should evaluate group policy or MDM controls to disable the feature in managed environments until Microsoft publishes enterprise-grade configuration guides and security assurances. Microsoft’s enterprise tooling historically provides toggles for inbox app behaviors; insist on documentation and control.

---

A close look at Microsoft’s trade-offs​

There are three competing priorities in the Notepad story: user convenience, platform safety, and product stability.

• Convenience drives Microsoft to add images: many users want a lightweight, always-available editor that can handle small documentation tasks without separate installs. Notepad with images would be a quick win for that use case.
• Platform safety argues for conservative design: given the live Markdown RCE incident, every interactive content surface must be hardened — and that hardening increases development cost and may delay releases.
• Product stability and code minimalism push back against feature creep: Notepad’s advantage has historically been small surface area and predictable behavior. Placing the app at the center of AI demos and formatting features risks alienating users who prize its simplicity.

How Microsoft balances these priorities will determine whether image support is a welcome quality-of-life improvement or another controversial step that fractures Notepad’s user base.

---

What Microsoft should do next (recommendations)​

If Microsoft wants this feature to succeed with minimal fallout, here are several practical steps it should take before wide release:

• Publish a clear technical design and security model that explains whether images are embedded, cached, or referenced; how remote fetches are handled; and what sanitization is applied to image metadata and links. Transparency reduces fear and increases adoption.
• Make the feature opt-in for default installs, or at minimum ship an enterprise policy that disables automatic image fetching and rendering. Many organizations require predictable offline workflows.
• Employ strict protocol whitelisting and neutralize unverified protocol handlers (the exact exploitation vector in the prior RCE). Do not allow Markdown interactions to call arbitrary protocols without explicit user consent and OS-level prompts.
• Limit image size by default and offer user controls for caching behavior to protect memory-constrained systems. Provide a view-only sandbox that prevents any embedded active content from executing.
• Document interoperability concerns and provide export/import tools so that Notepad-authored files remain compatible with mainstream Markdown toolchains used by developers and documentation teams.
• Continue subjecting Notepad’s update and fetch mechanics to rigorous supply-chain protections (signed packages, secure server validation) to prevent update/asset distribution abuse. Lessons from the Notepad++ update incident and others should guide stronger defaults.

---

Conclusion​

Adding image support to Notepad is a plausible and potentially useful next step in the app’s ongoing evolution from a minimal plain-text editor into a lightweight Markdown-first note and documentation tool. For developers, authors, and casual users who already embrace Markdown, inline images solve real problems and reduce friction for small documentation tasks.
But the change is not risk-free: the recent remote-code-execution vulnerability linked to Markdown rendering is a cautionary bell. Any image feature that fetches remote content, embeds binary data, or expands Notepad’s interactivity must be architected with explicit security and privacy safeguards, clear defaults that protect offline workflows, and transparent documentation that helps enterprises and power users make informed choices. Until Microsoft publishes those design details and ships robust controls, users should treat image-enabled Markdown in Notepad as a promising feature that still requires careful engineering and conservative rollout.
If Microsoft follows a conservative, well-documented approach — opt-in defaults, strong sanitization, and clear enterprise controls — images in Notepad could be a useful convenience rather than a regrettable case of feature creep. If the company rushes ahead without those protections, the next Notepad headline could easily be about a new stability or security incident rather than a productivity win. The community will watch closely as Insider builds evolve and Microsoft finally publishes the technical specifics that turn speculation into fact.

---

Source: TechSpot Microsoft is adding images to Notepad, and users are wondering why

 

[ChatGPT]

Microsoft’s decades‑old Notepad is quietly evolving again: Insider builds show an Insert image control and Markdown-aware rendering that point to inline image support arriving in Windows 11’s Notepad, a change that could reshape how users create quick notes, technical documentation, and Markdown-rich files.

Background​

Notepad has long been the ultimate minimalist text editor on Windows, prized for instant startup, tiny memory footprint, and straightforward plain‑text editing. Over the last two years Microsoft has been incrementally adding richer formatting and AI features to Notepad—Markdown support, basic text formatting (bold, italic, headings, lists), table insertion, and on‑device generative tools—delivered through Windows Insider preview channels so Microsoft can iterate quickly. These staged updates were packaged in preview releases such as Notepad version 11.2510.6.0 and distributed to Canary and Dev Windows Insider rings.
That trajectory explains why the recent appearance of an image icon in Notepad’s toolbar is significant: it’s the next logical step in a multi‑phase shift from bare plain text toward a lightweight Markdown authoring surface that supports multimedia inline rendering. Insiders spotted the icon in the app’s “What’s new” panel and screenshots in recent test flights. At the moment the control appears non‑functional in some internal builds, which is consistent with Microsoft’s practice of surfacing UI affordances early while backend implementation and safety checks are completed.

---

What’s new: image support, in practical terms​

What insiders have seen​

• A small insert image button appears in the Notepad formatting toolbar inside Insider builds and the app’s “What’s new” panel.
• The control is presented alongside existing Markdown formatting controls (bold, italic, headings, lists) and table insertion in preview builds, signaling that image handling is being tied to the Markdown/lightweight formatting layer already present in Notepad.
• Reports indicate the button is visible in current Insider flights but is not always fully functional; testing continues in internal branches. Microsoft has not posted a public announcement on the feature at the time of these Insider sightings.

Likely user experience (based on UI cues)​

• Insert images inline inside a text document, where the image is rendered in place rather than shown as a separate attachment or link.
• Image insertion tied to Markdown syntax—either via the editor’s formatting toolbar or by producing Markdown image links (e.g.,
  
  ) with automatic rendering in the app preview.
• An option to keep Notepad in a simplified, plaintext mode remains available via settings so users who prefer the classic Notepad experience can disable the richer formatting layer.

These functional expectations remain partially inferred from Insider screenshots and release notes; Microsoft has not finalized public documentation or a full feature matrix, so we flag details that are not yet verified with caution.

---

Why Microsoft is adding images to Notepad​

Microsoft’s broader strategy for Windows inbox apps is clear: evolve lightweight utilities into modern authoring surfaces that interoperate with Copilot and other AI features, retain low friction for casual use, and provide richer capabilities for documentation and knowledge work. Multiple recent Notepad updates—Markdown parity, tables, and streaming AI output—show Microsoft aiming to make Notepad a convenient place to author quick, richly formatted notes without forcing users into heavier apps. Image embedding is a natural extension of that work and helps Notepad serve use cases such as:

• Quick illustrated notes or checklists
• Technical documentation and README drafts with inline screenshots or diagrams
• Markdown‑first note taking that includes multimedia
• Mixed text + image notes for nontechnical users who prefer a single lightweight editor

Insider reporting describes this as a product decision informed by the removal of certain legacy apps and the need to consolidate lightweight editing features into a single, maintainable inbox editor. The evolution is being staged carefully through Insider channels to balance functionality, performance, and compatibility.

---

How it appears to work technically​

Integration with the Markdown/formatting layer​

The image control is surfaced inside Notepad’s existing formatting toolbar, which already maps to a lightweight Markdown engine in newer builds. That suggests one of two likely architectures:

• The editor inserts Markdown image references (local file paths or relative links) and renders them using the built‑in Markdown renderer.
• The editor embeds images inline using a richer document model (for example, a Markdown+/HTML rendering layer) while still offering a plaintext fallback when the formatting layer is disabled.

Either approach must reconcile the historical Notepad expectation of saving plain .txt files with the reality of embedded binary content. Microsoft’s prior updates preserved the option to remain in plaintext mode; image embedding will almost certainly be optional and constrained to the formatting-enabled mode.

File formats and storage​

• If Notepad inserts Markdown image references pointing to external files, the edited document can remain a plain .md or .txt file but depends on external image files for rendering.
• If Notepad supports embedded images (base64 or containerized blobs), the on‑disk format may shift away from pure plaintext—this has implications for portability, backup, and tools that assume ASCII/UTF‑8 text.
  At this stage the Insider artifacts indicate a rendering affordance rather than a fully documented storage model, so specifics around whether images are embedded or linked remain unconfirmed. We recommend treating early reports about on‑disk format as tentative until Microsoft publishes official documentation.

Performance and resource considerations​

Microsoft’s internal notes to Insiders reportedly claim “minimal impact” on performance for this feature in early tests, a reasonable but not definitive claim given a broad range of hardware and different image sizes users might insert. Notepad’s long history as an ultra‑light app sets a high bar: even modest image rendering increases memory use, GPU/CPU work for drawing, and potential I/O when embedding large images. Microsoft will need to balance responsiveness and memory footprint for low‑end hardware and resource‑constrained contexts.

---

Security, compatibility, and enterprise considerations​

Security surface and attack surface expansion​

Any feature that accepts, parses, or renders image files creates new parsing code and dependencies—JPEG, PNG, GIF decoders, and possibly SVG/HTML renderers. Those are frequently targeted vectors for exploitation in other software ecosystems, so enterprise security teams should understand the attack surface implications of enabling Notepad’s image rendering:

• Image decoders have a long history of memory corruption vulnerabilities; sandboxing and safe decoding libraries will be important.
• If Notepad downloads or links to remote image URIs automatically, it raises concerns about telemetry, exfiltration, and link‑preview privacy.
• Embedded metadata (EXIF) can contain sensitive information; Notepad will need to include controls or warnings if it exposes such metadata.

Microsoft’s insider messaging about “minimal impact” should not be taken as a complete security assurance; enterprises should wait for public documentation and security guidance before enabling these features widely in managed environments.

File compatibility and toolchain impacts​

• Developers and sysadmins rely on Notepad for editing configuration files, scripts, and logs in plain text. If Notepad documents begin to incorporate images or non‑plaintext content, compatibility with command‑line tools, version control, and configuration management could be affected.
• Microsoft appears to preserve a simplified plaintext mode that can be turned on in settings; organizations that require pure ASCII/UTF‑8 text editing should lock down Notepad settings or standardize on alternative tools like Notepad++ or other editor choices in managed images.

Policy and deployment options​

Enterprises will likely want:

• Group Policy or MDM controls to disable Notepad’s rich formatting and image rendering.
• Guidance on file formats produced by the new Notepad mode and how those files should be handled by backup and DLP systems.
• Clear endpoints for reporting security issues if new image handling code introduces vulnerabilities.

At present there is no public administrative documentation for image support in Notepad; cautious IT teams should treat the capability as experimental until Microsoft publishes deployment guidance.

---

User reaction and community response​

Notepad’s change has provoked mixed reactions that reflect two very different user groups.

• Power users, developers, and sysadmins: Many value Notepad specifically for its minimalism and predictability. There is concern that adding images and richer formatting erodes the app’s historic role as a tiny, reliable plaintext editor and could introduce ambiguity in workflows that depend on raw text editing. Some will prefer alternatives such as Notepad++ or other specialized editors that remain focused on code and plaintext.
• Casual users, note‑takers, and documentation creators: Others welcome the change; for these users Notepad with inline images becomes a no‑friction place to capture a screenshot, add a caption, and save a Markdown note without opening a heavier app. Notepad’s presence in the Windows inbox and its fast startup are compelling for ad‑hoc note capture workflows.

Microsoft’s decision to allow a simplified mode to be re‑enabled is critical here: it enables a dual approach where Notepad remains a tiny plaintext tool for old‑school users while adding optional capabilities for modern note tasks. That toggling will likely determine whether the change is broadly accepted or resisted.

---

Alternatives and workflow recommendations​

If you’re a Notepad loyalist who edits config files or writes small scripts, consider the following practical steps as the feature rolls through Insider and into broader release:

• Keep Notepad in plaintext mode. Use the app’s settings to disable the lightweight formatting layer and image rendering where available.
• Standardize on a trusted code editor for developer workflows. Tools like Notepad++ (or other code editors) remain ideal for syntax highlighting, plugins, and predictable plaintext handling.
• For Markdown + images, use purpose‑built note apps if you require robust syncing, attachments, and versioning (for example, specialized Markdown editors or note platforms).
• Validate the on‑disk file format before adopting Notepad‑created files in automated pipelines. If Notepad begins embedding binary content, your CI, backup, or deployment tools may need adjustments.

For power users who want to experiment, install Notepad from the Microsoft Store on a test machine and enroll in Windows Insider channels to try Canary/Dev builds, providing feedback through the Insider feedback channels. Expect features to move slowly from Canary to Dev and eventually to public release if testing is successful.

---

Risks and open questions​

The Notepad image support announcement (via Insider eyes) raises a number of unanswered questions that Windows users and IT teams should watch carefully:

• On‑disk format: Will Notepad continue to save pure .txt files when images are inserted? Or will it switch to .md/.rtf/.notepadx (hypothetical) formats or embed images inside the file? Current signals are ambiguous and must be confirmed by Microsoft documentation.
• Security hardening: What image decoding libraries will Notepad use? Will the image renderer be sandboxed or rely on system components that can be updated separately? Early insider messaging about “minimal impact” is encouraging but not comprehensive.
• Interoperability: How will Notepad behave when opening files that include images on systems that do not have the new formatting layer (older Windows or Linux text tools)? Will the app provide graceful degradation or produce unreadable output for plain text processors?
• Privacy and remote content: If Notepad supports remote image URLs, will it preload or fetch images automatically, and will that behavior be controllable? Automatic fetches could reveal internal IPs or create privacy concerns. This is currently speculative and merits vendor confirmation.

We flag these as important because they affect security, compliance, and automation. Until Microsoft publishes detailed technical and security documentation, treat specific claims about on‑disk formats, decoder choices, and default network behavior as provisional and experimental.

---

The product tradeoffs: feature creep vs. utility​

Notepad’s evolution is a textbook example of a classic product tension: preserve simplicity or add utility. There are real benefits to richer Notepad features:

• Faster, simpler authoring for many everyday tasks
• Consolidation of lightweight editing capability into a single, discoverable inbox app
• Better parity with modern workflows that expect Markdown and inline media

But there are clear tradeoffs:

• Increased complexity and potential confusion for users who expect a pure text scratchpad
• Expanded security surface and maintenance burden for Microsoft
• Possible incompatibilities with tooling that assumes plain text

Microsoft’s current approach—rolling features behind an opt‑in formatting layer and exposing toggles—reflects a pragmatic compromise. If executed well, Notepad can serve two audiences with minimal disruption; if executed poorly, it risks alienating longtime Notepad users and introducing avoidable security or compatibility issues. Insider feedback will be the decisive factor.

---

Practical timeline and what to watch for​

• Canary/Dev preview sightings suggest the image control is already present in Insider builds; these builds are the earliest testing ground and often change rapidly. Expect continued iterations in Canary, then staged promotion to Dev and Beta rings if testing is positive.
• Microsoft typically publishes release notes and documentation when features reach broader release; watch for an official Notepad update announcement that explains file formats, administrative controls, and security hardening details.
• Enterprise admins should look for Group Policy and MDM controls that disable formatting/image features before enabling the feature in managed images. Such controls commonly follow major inbox app changes but are not guaranteed at initial release.

---

Conclusion​

The arrival of an insert image control in Windows 11 Notepad Insider builds marks a consequential step in the app’s transformation from minimalist scratchpad to a lightweight, Markdown‑aware authoring surface. The practical upside is obvious: faster, simpler creation of illustrated notes, README drafts, and mixed multimodal documents directly within Notepad. The potential downsides—security surface expansion, file format ambiguity, and a breach of the expectations that made Notepad indispensable—are equally real.
For now, image support in Notepad remains an Insider‑level test: visible in UI panels and screenshots but not yet fully documented or widely shipped. Users who depend on pure plaintext workflows should treat the change cautiously and use the available settings to preserve the classic Notepad experience. Enterprise teams should await official administrative guidance and carefully evaluate the feature in isolated test environments before rolling it into production images.
Microsoft’s careful, iterative approach—surface UI affordances to gather feedback, provide toggles to retain plaintext, and route changes through Insider rings—gives it a chance to strike a balance. Whether Notepad becomes a beloved modern note utility or a controversial departure from minimalism depends on the implementation details Microsoft publishes next: file storage behavior, security hardening, and administrative controls. Until those details are public, treat image support as a promising but experimental evolution of Windows’ oldest text box.

---

Source: hi-Tech.ua Microsoft adds image support to Notepad