\ud83e\uddf1 Breaking changes<\/h3>\n
Legacy Paper Support Removed<\/p>\n
If your application is still running on the Paper architecture, it will not work with React Native Windows v0.82.<\/p>\n
This change aligns with Meta’s broader direction for React Native, where the Old Architecture is being deprecated and removed across all platforms. By moving to Fabric now, your application is positioned for continued support, improved performance, and access to all future platform features.<\/p>\n
\ud83d\udd25 What\u2019s New in RNW v0.82?\n<\/span><\/span><\/h3>\n\nEnable XAML Controls in Community Modules on New Architecture<\/strong><\/div>\n\n- One of the most requested capabilities for React Native Windows has arrived: community modules can now use native XAML controls within the Fabric (New Architecture) renderer.<\/li>\n
- Previously, integrating native Windows XAML controls \u2014 such as calendar, pickers or custom enterprise controls \u2014 into a React Native Windows app required workarounds or was limited to the legacy Paper architecture. With v0.82, this barrier is removed.<\/li>\n
- How it works: Community and third-party module authors can now create native components that render XAML controls directly inside the Fabric component tree. This means your Windows app can mix React components and native XAML controls side by side, with proper layout, hit-testing, and accessibility support.<\/li>\n
- Why this matters: Richer Windows experiences – Use the full power of the Windows XAML control library \u2014 including WinUI controls, custom controls, and platform-specific UI \u2014 right alongside your React components.<\/li>\n
- Unblocks community modules – Module authors no longer need to wait for every control to be re-implemented in Composition. They can wrap existing XAML controls and expose them as React Native components.<\/li>\n
- Smooth interop – XAML controls hosted this way participate in the standard React Native layout and rendering pipeline, so they behave predictably alongside other components.<\/li>\n<\/ul>\n\n\nAccessibility Override for Third-Party Modules<\/strong><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n
\n- React Native Windows v0.82 introduces a new accessibility override API for third-party (3P) modules, giving module authors fine-grained control over how their custom native components are exposed to screen readers and assistive technologies.<\/li>\n
- Previously, custom native components in community modules inherited default accessibility behavior from the framework, with limited ability to customize properties like roles, labels, live regions, or automation IDs. This made it difficult for module authors to deliver fully accessible experiences \u2014 especially for complex controls that don’t map neatly to built-in component types.<\/li>\n
- How it works: Module authors can now override the default accessibility provider for their custom native components. This lets you define exactly how your component is announced by a screen reader, which UI Automation (UIA) properties it exposes, and how it responds to accessibility queries \u2014 all without modifying the core framework.<\/li>\n
- Why this matters: Fully accessible community modules – Module authors can ensure their components work correctly with Narrator, and other Windows assistive technologies out of the box.<\/li>\n
- Custom roles and properties – Define custom UIA roles, labels, and states that accurately describe your component’s purpose and behavior to users who rely on assistive technology.<\/li>\n
- Better end-user experience – Apps that use third-party modules can now deliver a consistent, accessible experience across all components \u2014 both built-in and community-provided.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n
\u2699\ufe0f Component Enhancements<\/span><\/span><\/h3>\n <\/p>\n
\n\nRecent enhancements to React Native Windows v0.82 bring a host of new capabilities and parity improvements to core components, aimed at delivering a smoother, more complete, and accessible user experience.<\/p>\n
\nText<\/strong><\/div>\n\n- Text selection support for Fabric Text components \u2014 users can now select and copy text content.<\/li>\n
- Overflow handling improvements, giving developers more control over how text behaves when it exceeds its container.<\/li>\n
- selectionColor support for Fabric Text, allowing customization of the text selection highlight color.<\/li>\n<\/ul>\nTextInput<\/strong><\/div>\n
\n- Selection prop support \u2014 programmatic control over cursor position and text selection range.<\/li>\n
- textAlign support \u2014 align text content (left, center, right) within the input.<\/li>\n
- writingDirection support \u2014 set the writing direction (LTR\/RTL) for internationalized apps.<\/li>\n
- Italic, underline, and strikethrough styling \u2014 apply rich text formatting directly to TextInput content.<\/li>\n<\/ul>\nScrollView<\/strong><\/div>\n
\n- pagingEnabled parity \u2014 ScrollView now supports page-based snapping behavior, aligned with iOS and Android, enabling swipeable page layouts and carousels.<\/li>\n<\/ul>\nContextMenu<\/strong><\/div>\n
\n- ContextMenu implementation in Fabric \u2014 right-click \/ long-press context menus are now available in the New Architecture, enabling standard Windows interaction patterns within your React Native app.<\/li>\n<\/ul>\nAccessibility<\/strong><\/div>\n
\n- Deferred initialization of UIA accessibility providers \u2014 accessibility providers is now initialized on demand rather than upfront, resulting in improved startup performance for apps with large component trees.<\/li>\n
- UI Automation (UIA) improvements for XAML Fabric \u2014 better integration between Fabric-rendered components and the Windows UI Automation framework, ensuring screen readers and assistive technologies work correctly.<\/li>\n
- Ability to customize native accessibility for custom native components \u2014 module authors and app developers can now override and fine-tune the accessibility properties exposed by their custom native components.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/react-native\/wp-content\/uploads\/sites\/76\/2026\/03\/Screenshot-2026-03-24-162544-300x148.webp\")
<\/a><\/p>\n\ud83d\udd27 Reliability & Stability<\/h2>\n\nImmense effort went into making apps more robust in this release. Key fixes include:<\/div>\n\n- Fixed crashes when switching bundles \u2014 apps that dynamically load different JS bundles no longer crash during the transition.<\/li>\n
- Fixed crashes when loading images offline \u2014 image components handle network unavailability gracefully instead of crashing.<\/li>\n
- Fixed crashes when closing modals \u2014 modal dismissal no longer triggers race conditions or null-reference crashes.<\/li>\n
- DevTools overlays now behave correctly on high-DPI displays \u2014 layout and positioning of developer tool overlays are now accurate across different display scale factors.<\/li>\n
- Tooltip positioning corrected across scale factors \u2014 tooltips render at the correct screen location regardless of the display’s DPI setting.<\/li>\n
- Improved handling of accessibility properties (e.g., `UIA_LiveSettingPropertyId`) \u2014 live region announcements and dynamic content updates are now reported correctly to screen readers.<\/li>\n
- Improved inspector page naming in the modern debugger\u2014 DevTools inspector pages now display clearer, more descriptive names, making it easier to identify and debug specific components.<\/li>\n<\/ul>\n<\/div>\n
\ud83d\udcca Feature Parity Progress<\/h2>\n
With the removal of Paper and the consolidation on Fabric, all core components, APIs, and functionality are now being delivered exclusively through the New Architecture. This release closes several remaining parity gaps:<\/p>\n
\n- Text selection, overflow, and selectionColor for Text components<\/li>\n
- ScrollView pagingEnabled<\/li>\n
- TextInput selection, textAlign, and writingDirection<\/li>\n
- ContextMenu in Fabric<\/li>\n
- Rich text styling (italic, underline, strikethrough) for TextInput<\/li>\n<\/ul>\n
If you encounter missing properties or functionality, please open an issue<\/a>. You can also leave comments on existing issues to help us prioritize what to tackle next!<\/p>\n\nKnown Limitation<\/strong><\/div>\n\n- keyboardType\u2014 The `keyboardType` prop is supported but has limitations on Windows. Not all keyboard type values behave identically to iOS and Android due to platform differences in soft keyboard handling. See issue #15572<\/a> for details and current status.<\/li>\n<\/ul>\n<\/div>\n
\ud83d\udd17 For a full list of known gaps, see: Missing Properties \u00b7 React Native for Windows<\/a><\/p>\n <\/p>\n
\n\ud83c\udfc1 Gallery App Updates<\/h2>\n
Install the latest React Native Gallery (0.82) to explore all the new features and component enhancements in action.<\/p>\n
Search “React Native Gallery” in the Microsoft Store or use the direct link<\/a>.\nThe Gallery app now runs exclusively on the Fabric renderer, reflecting the Fabric-only direction of the platform.<\/p>\nThe Gallery app is the best way to see how each component looks and behaves on Windows, and we encourage you to use it as a reference when building or migrating your own apps.<\/p>\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/react-native\/wp-content\/uploads\/sites\/76\/2026\/03\/Screenshot-2026-03-24-163409-296x300.webp\")
<\/a><\/p>\n<\/div>\n\ud83d\udce6 Release Details<\/h2>\n\n- Version: React Native Windows v0.82.0<\/li>\n
- Released: March 17, 2026<\/li>\n
- Covers commits: August 2, 2025 \u2013 January 15, 2026 github.com<\/a><\/li>\n<\/ul>\n
\ud83d\udd17 Reference Links<\/h2>\n\n- React Native Windows Documentation<\/a><\/li>\n
- React Native Windows GitHub<\/a><\/li>\n
- Fabric Architecture Overview<\/a><\/li>\n
- Migration Guide (Paper \u2192 Fabric)<\/a><\/li>\n
- Upgrading Your App<\/a><\/li>\n<\/ul>\n
If you’re interested in getting started with React Native for Windows, check out our website at aka.ms\/reactnative<\/a>.<\/p>\n
- \n
- One of the most requested capabilities for React Native Windows has arrived: community modules can now use native XAML controls within the Fabric (New Architecture) renderer.<\/li>\n
- Previously, integrating native Windows XAML controls \u2014 such as calendar, pickers or custom enterprise controls \u2014 into a React Native Windows app required workarounds or was limited to the legacy Paper architecture. With v0.82, this barrier is removed.<\/li>\n
- How it works: Community and third-party module authors can now create native components that render XAML controls directly inside the Fabric component tree. This means your Windows app can mix React components and native XAML controls side by side, with proper layout, hit-testing, and accessibility support.<\/li>\n
- Why this matters: Richer Windows experiences – Use the full power of the Windows XAML control library \u2014 including WinUI controls, custom controls, and platform-specific UI \u2014 right alongside your React components.<\/li>\n
- Unblocks community modules – Module authors no longer need to wait for every control to be re-implemented in Composition. They can wrap existing XAML controls and expose them as React Native components.<\/li>\n
- Smooth interop – XAML controls hosted this way participate in the standard React Native layout and rendering pipeline, so they behave predictably alongside other components.<\/li>\n<\/ul>\n\n\nAccessibility Override for Third-Party Modules<\/strong><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n
- \n
- React Native Windows v0.82 introduces a new accessibility override API for third-party (3P) modules, giving module authors fine-grained control over how their custom native components are exposed to screen readers and assistive technologies.<\/li>\n
- Previously, custom native components in community modules inherited default accessibility behavior from the framework, with limited ability to customize properties like roles, labels, live regions, or automation IDs. This made it difficult for module authors to deliver fully accessible experiences \u2014 especially for complex controls that don’t map neatly to built-in component types.<\/li>\n
- How it works: Module authors can now override the default accessibility provider for their custom native components. This lets you define exactly how your component is announced by a screen reader, which UI Automation (UIA) properties it exposes, and how it responds to accessibility queries \u2014 all without modifying the core framework.<\/li>\n
- Why this matters: Fully accessible community modules – Module authors can ensure their components work correctly with Narrator, and other Windows assistive technologies out of the box.<\/li>\n
- Custom roles and properties – Define custom UIA roles, labels, and states that accurately describe your component’s purpose and behavior to users who rely on assistive technology.<\/li>\n
- Better end-user experience – Apps that use third-party modules can now deliver a consistent, accessible experience across all components \u2014 both built-in and community-provided.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n
\u2699\ufe0f Component Enhancements<\/span><\/span><\/h3>\n
<\/p>\n
\n\nRecent enhancements to React Native Windows v0.82 bring a host of new capabilities and parity improvements to core components, aimed at delivering a smoother, more complete, and accessible user experience.<\/p>\n
\nText<\/strong><\/div>\n- \n
- Text selection support for Fabric Text components \u2014 users can now select and copy text content.<\/li>\n
- Overflow handling improvements, giving developers more control over how text behaves when it exceeds its container.<\/li>\n
- selectionColor support for Fabric Text, allowing customization of the text selection highlight color.<\/li>\n<\/ul>\nTextInput<\/strong><\/div>\n
- \n
- Selection prop support \u2014 programmatic control over cursor position and text selection range.<\/li>\n
- textAlign support \u2014 align text content (left, center, right) within the input.<\/li>\n
- writingDirection support \u2014 set the writing direction (LTR\/RTL) for internationalized apps.<\/li>\n
- Italic, underline, and strikethrough styling \u2014 apply rich text formatting directly to TextInput content.<\/li>\n<\/ul>\nScrollView<\/strong><\/div>\n
- \n
- pagingEnabled parity \u2014 ScrollView now supports page-based snapping behavior, aligned with iOS and Android, enabling swipeable page layouts and carousels.<\/li>\n<\/ul>\nContextMenu<\/strong><\/div>\n
- \n
- ContextMenu implementation in Fabric \u2014 right-click \/ long-press context menus are now available in the New Architecture, enabling standard Windows interaction patterns within your React Native app.<\/li>\n<\/ul>\nAccessibility<\/strong><\/div>\n
- \n
- Deferred initialization of UIA accessibility providers \u2014 accessibility providers is now initialized on demand rather than upfront, resulting in improved startup performance for apps with large component trees.<\/li>\n
- UI Automation (UIA) improvements for XAML Fabric \u2014 better integration between Fabric-rendered components and the Windows UI Automation framework, ensuring screen readers and assistive technologies work correctly.<\/li>\n
- Ability to customize native accessibility for custom native components \u2014 module authors and app developers can now override and fine-tune the accessibility properties exposed by their custom native components.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n<\/a><\/p>\n
\ud83d\udd27 Reliability & Stability<\/h2>\n
\nImmense effort went into making apps more robust in this release. Key fixes include:<\/div>\n- \n
- Fixed crashes when switching bundles \u2014 apps that dynamically load different JS bundles no longer crash during the transition.<\/li>\n
- Fixed crashes when loading images offline \u2014 image components handle network unavailability gracefully instead of crashing.<\/li>\n
- Fixed crashes when closing modals \u2014 modal dismissal no longer triggers race conditions or null-reference crashes.<\/li>\n
- DevTools overlays now behave correctly on high-DPI displays \u2014 layout and positioning of developer tool overlays are now accurate across different display scale factors.<\/li>\n
- Tooltip positioning corrected across scale factors \u2014 tooltips render at the correct screen location regardless of the display’s DPI setting.<\/li>\n
- Improved handling of accessibility properties (e.g., `UIA_LiveSettingPropertyId`) \u2014 live region announcements and dynamic content updates are now reported correctly to screen readers.<\/li>\n
- Improved inspector page naming in the modern debugger\u2014 DevTools inspector pages now display clearer, more descriptive names, making it easier to identify and debug specific components.<\/li>\n<\/ul>\n<\/div>\n
\ud83d\udcca Feature Parity Progress<\/h2>\n
With the removal of Paper and the consolidation on Fabric, all core components, APIs, and functionality are now being delivered exclusively through the New Architecture. This release closes several remaining parity gaps:<\/p>\n
- \n
- Text selection, overflow, and selectionColor for Text components<\/li>\n
- ScrollView pagingEnabled<\/li>\n
- TextInput selection, textAlign, and writingDirection<\/li>\n
- ContextMenu in Fabric<\/li>\n
- Rich text styling (italic, underline, strikethrough) for TextInput<\/li>\n<\/ul>\n
If you encounter missing properties or functionality, please open an issue<\/a>. You can also leave comments on existing issues to help us prioritize what to tackle next!<\/p>\n
\nKnown Limitation<\/strong><\/div>\n- \n
- keyboardType\u2014 The `keyboardType` prop is supported but has limitations on Windows. Not all keyboard type values behave identically to iOS and Android due to platform differences in soft keyboard handling. See issue #15572<\/a> for details and current status.<\/li>\n<\/ul>\n<\/div>\n
\ud83d\udd17 For a full list of known gaps, see: Missing Properties \u00b7 React Native for Windows<\/a><\/p>\n
<\/p>\n
\n\ud83c\udfc1 Gallery App Updates<\/h2>\n
Install the latest React Native Gallery (0.82) to explore all the new features and component enhancements in action.<\/p>\n
Search “React Native Gallery” in the Microsoft Store or use the direct link<\/a>.\nThe Gallery app now runs exclusively on the Fabric renderer, reflecting the Fabric-only direction of the platform.<\/p>\n
The Gallery app is the best way to see how each component looks and behaves on Windows, and we encourage you to use it as a reference when building or migrating your own apps.<\/p>\n
<\/a><\/p>\n<\/div>\n\ud83d\udce6 Release Details<\/h2>\n
- \n
- Version: React Native Windows v0.82.0<\/li>\n
- Released: March 17, 2026<\/li>\n
- Covers commits: August 2, 2025 \u2013 January 15, 2026 github.com<\/a><\/li>\n<\/ul>\n
\ud83d\udd17 Reference Links<\/h2>\n
- \n
- React Native Windows Documentation<\/a><\/li>\n
- React Native Windows GitHub<\/a><\/li>\n
- Fabric Architecture Overview<\/a><\/li>\n
- Migration Guide (Paper \u2192 Fabric)<\/a><\/li>\n
- Upgrading Your App<\/a><\/li>\n<\/ul>\n
If you’re interested in getting started with React Native for Windows, check out our website at aka.ms\/reactnative<\/a>.<\/p>\n
- React Native Windows GitHub<\/a><\/li>\n
- React Native Windows Documentation<\/a><\/li>\n
- keyboardType\u2014 The `keyboardType` prop is supported but has limitations on Windows. Not all keyboard type values behave identically to iOS and Android due to platform differences in soft keyboard handling. See issue #15572<\/a> for details and current status.<\/li>\n<\/ul>\n<\/div>\n
- ContextMenu implementation in Fabric \u2014 right-click \/ long-press context menus are now available in the New Architecture, enabling standard Windows interaction patterns within your React Native app.<\/li>\n<\/ul>\n
- pagingEnabled parity \u2014 ScrollView now supports page-based snapping behavior, aligned with iOS and Android, enabling swipeable page layouts and carousels.<\/li>\n<\/ul>\n