What’s new for developers? (June 2026)  🔗 **Source:** [What’s new for developers? (June 2026)](https://developer.wordpress.org/news/2026/06/whats-new-for-developers-june-2026/) > [!note]+ Document Notes > tags: [wordpress-development, block-editor, ai-integration, playground-tools, accessibility, developer-updates] > author: Fatih Kadir Akın > source: WordPress Developer Blog > reference: https://developer.wordpress.org/news/2026/06/whats-new-for-developers-june-2026/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: What's new for developers? (June 2026) > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ## 📝 Summary - WordPress 7.0 "Armstrong" launched May 20, 2026, with significant updates to AI APIs, block registration, DataViews, and accessibility features. - June 2026 brings major developer-facing changes including client-side media processing, React 19 compatibility work, and collaborative editing progress for WordPress 7.1. - Key technical shifts include deprecation of wp-now in favor of Playground CLI, new pseudo-state styling for individual blocks, and expanded Unicode email support proposals. - WordPress Playground evolves with saved sites functionality, PR preview improvements, and PHP.wasm extension capabilities. - The accessibility and internationalization work continues with admin color-scheme improvements and Unicode email address support under consideration. ## 📖 Main Content WordPress development in June 2026 centers around stabilizing the WordPress 7.0 release while preparing significant infrastructure changes for 7.1. The most impactful changes affect how developers work with media processing, collaborative editing, and local development environments. ### Media Processing Revolution Client-side media processing represents a fundamental shift in how WordPress handles images. The new VIPS/WASM pipeline processes images in the browser when possible, generating thumbnails and sub-sizes without server round-trips. This affects AVIF, WebP, HEIC, Ultra HDR, JPEG XL formats, and includes GIF-to-video conversion capabilities. The implementation includes intelligent fallbacks - it's disabled on devices with 2GB RAM or less, bypassed on slow connections, and skipped when restrictive Content Security Policy worker-src settings are detected. Currently active only in Chromium browsers with the latest Gutenberg plugin. ### React 19 Migration Challenges The React 19 upgrade faced significant compatibility issues, leading to a temporary revert. Multiple plugins bundled React 18 JSX runtime helpers that crashed when loaded alongside React 19. The Core team now plans a more incremental strategy for WordPress 7.1. Plugin authors need to prepare for: eliminating render() and hydrate() usage, replacing unmountComponentAtNode(), avoiding findDOMNode(), reviewing ref callbacks, and updating TypeScript configurations. ### Collaborative Editing Progress Real-time collaboration didn't ship with WordPress 7.0, but active development continues for 7.1. The collaborative editing outreach effort targets plugins that store editor state, use meta boxes, modify block editor data, or depend on save behavior. ### Playground Infrastructure Maturation WordPress Playground deprecated wp-now in favor of the Playground CLI, marking a significant tooling shift for local development. The platform now supports saved sites with persistence across sessions, PR preview workflows, and runnable PHP examples in documentation. Recent updates include Sites API documentation, autosave restore UX, and support for historical WordPress versions back to 0.7 through the Virtual WordPress Museum. ## 🗒️ Notes - **WordPress 7.0 "Armstrong"** launched May 20, 2026, with major updates to AI APIs, block registration, DataViews, block bindings, editor UI, design tools, and accessibility - **Media editor modal** now defaults for crop experiences with freeform and aspect-ratio cropping, flip, rotation, zoom, and metadata editing - **Client-side media processing** uses VIPS/WASM pipeline for browser-based image sub-size generation with server fallbacks - **React 19 compatibility** temporarily reverted due to plugin crashes; incremental strategy planned for WordPress 7.1 - **Abilities API refinements** include lifecycle filters, input/output validation, expanded REST schema, and keyword handling - **PHP support clarification** retires "beta support" label; minimum supported version remains 7.4, recommended 8.3 - **Unicode email support** proposal extends support to email addresses, usernames, and slugs affecting is_email(), sanitize_email(), and antispambot() - **Pseudo-state styling** enables :hover, :focus, :visited states on individual block instances without site-wide changes - **wp-now deprecation** in favor of Playground CLI for local WordPress environments - **Collaborative editing** outreach begins for WordPress 7.1 testing with latest Gutenberg plugin - **Dashboard customization** experiment adds five new widgets with layout improvements and container-breakpoint grid columns - **Accessibility improvements** include admin color-scheme contrast, frontend toolbar focus outlines, and high contrast button fixes ## 📚 References - [WordPress 7.0 Field Guide](https://make.wordpress.org/core/2026/05/20/wordpress-7-0-field-guide/) - [Media Editor Modal call for testing](https://make.wordpress.org/test/2026/05/15/media-editor-modal-call-for-testing/) - [Client-side media processing call for testing](https://make.wordpress.org/test/2026/06/01/client-side-media-processing-call-for-testing/) - [React 19 upgrade dev note](https://make.wordpress.org/core/2026/04/15/react-19-upgrade-dev-note/) - [Collaborative editing outreach for 7.1](https://make.wordpress.org/test/2026/06/05/collaborative-editing-outreach-7-1/) - [Playground CLI documentation](https://wordpress.github.io/wordpress-playground/docs/playground-cli/) - [AI Client image generation tutorial](https://developer.wordpress.org/news/2026/06/how-to-build-image-generation-plugin-wordpress-ai-client/) ## 🗣️ Paraphrase WordPress development in June 2026 focuses on stabilizing the major WordPress 7.0 release while introducing transformative infrastructure changes for version 7.1. The month's updates center around three key areas: revolutionary client-side media processing that moves image operations to the browser, collaborative editing preparation that enables real-time multi-user editing, and Playground platform maturation that improves local development workflows. Plugin developers face important compatibility considerations, particularly around the React 19 upgrade that required temporary reversal due to runtime conflicts. The WordPress team is taking a more incremental approach to major framework updates while expanding accessibility improvements and Unicode support across the platform. ## 📰 Newsletter 🚀 **June WordPress Dev Update: Big Changes Ahead!** WordPress 7.0 "Armstrong" dropped in May, and June brought some game-changing updates for developers! Client-side media processing is here (goodbye server bottlenecks!), wp-now is officially deprecated in favor of Playground CLI, and collaborative editing is gaining momentum for 7.1. The React 19 upgrade hit some bumps and got temporarily reverted, but don't worry - the team's taking a smarter, incremental approach. Plus, Playground now supports saved sites that actually persist between sessions! **Must-try this month:** The new AI Client image generation tutorial and the upgraded media editor modal with aspect-ratio controls. Your themes and plugins deserve that accessibility polish pass too - the contrast improvements in WordPress 7.0 are worth checking out. **Quick wins:** Update your local dev setup to Playground CLI, test your image-heavy plugins against the new media processing pipeline, and give those pseudo-state block styles a spin in Gutenberg 23.3. Keep building awesome stuff! 🎯 ## ✅ Action Items #### DevRel - Create migration guide from wp-now to Playground CLI with video walkthrough - Develop React 19 compatibility workshop for plugin developers - Build demo showcasing client-side media processing capabilities and fallback behaviors - Document pseudo-state styling patterns for theme developers #### WordPress - **Core:** Coordinate React 19 incremental migration strategy with plugin ecosystem feedback - **Core Performance:** Monitor client-side media processing performance metrics and browser compatibility - **Core AI:** Expand AI Client tutorial library with additional use cases beyond image generation - **Community:** Create testing campaign for collaborative editing features targeting high-usage plugins - **Documentation:** Update PHP version support documentation removing "beta" language for PHP 8.x - **Accessibility:** Continue admin color-scheme contrast improvements across remaining admin screens - **Meta:** Implement Unicode email support proposal with comprehensive backwards compatibility testing #### Community - **Plugin authors:** Audit compiled JSX usage and React 18 runtime dependencies before React 19 migration - **Theme developers:** Test pseudo-state styling and responsive block controls in Gutenberg 23.3+ - **Hosting providers:** Evaluate client-side media processing impact on server load and CDN strategies ## 🧪 Hypotheses - Client-side media processing will reduce server load for image-heavy WordPress sites by 20-40% while improving user upload experience - The incremental React 19 migration approach will achieve higher plugin compatibility rates than the initial full upgrade attempt - Playground's saved sites functionality will increase developer adoption for testing and demonstration workflows - Unicode email support will improve WordPress accessibility for international users while maintaining backwards compatibility - Collaborative editing will drive increased Gutenberg plugin adoption when released in WordPress 7.1 - The deprecation of wp-now in favor of Playground CLI will consolidate local development tooling and reduce maintenance overhead ## 📊 Methodology - **Client-side media processing performance**: A/B testing with server-side processing baseline, measuring upload completion times, thumbnail generation speed, and server resource utilization across device types and connection speeds - **React 19 compatibility assessment**: Automated scanning of top 1000 WordPress plugins for React runtime dependencies, manual testing of high-usage plugins, and compatibility scorecard development - **Playground adoption metrics**: Tracking wp-now to Playground CLI migration rates, saved sites usage patterns, and developer workflow completion rates - **Unicode email support impact**: Compatibility testing across email providers, username validation systems, and database storage implementations ## ❓ Questions - How will client-side media processing affect WordPress hosting providers' resource allocation and pricing models? - What specific plugin architectures are most vulnerable to the React 19 upgrade challenges? - Can the collaborative editing system handle large documents with complex block structures without performance degradation? - How will Unicode email support interact with existing anti-spam and security plugins? - What are the long-term maintenance implications of supporting both server-side and client-side media processing pipelines? - Will Playground's browser-based WordPress instances eventually replace traditional local development environments? ## 🔮 Future Research - Performance impact analysis of client-side media processing on mobile devices and low-bandwidth connections - React 19 migration pathway optimization for complex plugin ecosystems - Collaborative editing conflict resolution strategies for concurrent block modifications - Unicode email support security implications and internationalization best practices - Playground architecture scalability for enterprise development workflows - Long-term viability of browser-based PHP execution for development tools ## 💡 Implications WordPress's move toward client-side processing and collaborative editing represents a fundamental architectural shift that will affect hosting requirements, plugin development patterns, and user experience expectations. The React 19 migration challenges highlight the complexity of maintaining backwards compatibility while advancing the platform's technical foundation. For hosting providers, client-side media processing could reduce server computational requirements while increasing browser compatibility considerations. Plugin developers must prepare for more sophisticated JavaScript runtime environments and potential breaking changes in core APIs. The Playground platform's evolution toward persistent browser-based WordPress instances could democratize WordPress development by lowering barrier to entry while providing more sophisticated testing and demonstration capabilities. ## 🧠 Learning Styles Assessment **Reading level estimate**: Grade 12-14 (Flesch-Kincaid) - Technical content with specialized WordPress terminology requiring developer background knowledge. #### 👀 Visual learners - **Present**: Code examples, technical diagrams, workflow illustrations - **Improve**: Add architecture diagrams for client-side media processing, React 19 migration flowcharts, visual comparison of wp-now vs Playground CLI workflows #### 🔊 Aural learners - **Present**: None identified - **Improve**: 5-minute podcast summary of key changes, audio walkthrough of new features, developer interview about React 19 challenges #### 🗣️ Verbal learners - **Present**: Clear technical definitions, step-by-step explanations, numbered procedures - **Improve**: Add glossary section, provide analogies for complex concepts like VIPS/WASM pipeline #### 🧩 Kinesthetic learners - **Present**: Testing calls, hands-on tutorials, interactive examples via Playground - **Improve**: Provide downloadable test cases, checklist-based migration guides, sandbox environments for each feature #### 🧠 Logical learners - **Present**: Structured table of contents, logical progression from features to implementation details - **Improve**: Add decision trees for feature adoption, compatibility matrices, performance benchmarking criteria #### 🧑‍🤝‍🧑 Social learners - **Present**: Community testing calls, collaboration features, peer review mentions - **Improve**: Discussion prompts, community feedback channels, collaborative testing groups #### 🧘‍♀️ Solitary learners - **Present**: Comprehensive documentation links, self-guided tutorials - **Improve**: Personal reflection questions, individual testing checklists, private progress tracking #### 🌿 Naturalistic learners - **Present**: Ecosystem thinking, compatibility considerations, organic feature evolution - **Improve**: WordPress ecosystem impact analysis, sustainability considerations for client-side processing ## 📊 Accessibility Assessment #### Screen reader semantics - **Present**: Proper heading hierarchy, descriptive section titles - **Improve**: Add aria-labels for code examples, ensure alt text for any embedded media, provide skip navigation for long technical sections #### Keyboard navigation - **Present**: Standard web navigation patterns - **Improve**: Ensure all interactive examples are keyboard accessible, add focus indicators for code blocks #### Contrast and readability - **Present**: Standard blog formatting with adequate contrast - **Improve**: Verify code syntax highlighting meets contrast requirements, ensure link visibility #### Text resizing and reflow - **Present**: Responsive design supports text scaling - **Improve**: Test technical content at 200% zoom, ensure code blocks remain readable #### Media and captions - **Present**: No embedded video/audio content identified - **Improve**: Add captions if videos are later embedded, provide transcripts for audio content #### Forms and interactions - **Present**: Standard comment form with labels - **Improve**: No significant improvements needed for current form implementation #### Standards reference - Meets WCAG 2.2 AA standards for informational content, could improve with enhanced semantic markup for code examples ## 🌍 DEIB Assessment #### Cultural breadth - **Present**: Global WordPress community perspective, international Unicode considerations - **Improve**: Include examples from diverse geographic regions, highlight non-English WordPress usage patterns #### Inclusive language - **Present**: Technical terminology appropriately defined, gender-neutral language - **Improve**: Provide more context for technical abbreviations, expand glossary for non-native English speakers #### Neurodiversity support - **Present**: Clear structure, consistent formatting, logical information flow - **Improve**: Add summary boxes for key points, provide multiple explanation formats for complex concepts #### Representation - **Present**: Technical content focuses on functionality rather than individual representation - **Improve**: Include diverse contributor acknowledgments, highlight global community participation #### Psychological safety - **Present**: Professional tone, constructive approach to challenges like React 19 revert - **Improve**: Acknowledge learning curve concerns, provide supportive migration guidance ## ✅ Logical Validity #### Strong reasoning - **Deductive reasoning**: Clear cause-effect relationships between React 19 JSX runtime conflicts and plugin crashes, with logical progression to incremental migration strategy - **Inductive reasoning**: Pattern recognition from testing feedback leading to broader conclusions about client-side processing viability - **Causal reasoning**: Direct correlation between browser capabilities and client-side media processing fallback behavior #### Fallacies - **Appeal to novelty**: Some features presented as beneficial primarily because they're new rather than demonstrating clear advantages - **False dichotomy**: wp-now vs Playground CLI presented as binary choice without acknowledging transition period needs #### Tone of voice Professional and informative with technical authority. Uses inclusive "we" language and acknowledges challenges honestly while maintaining optimistic outlook for platform evolution. ## 🛡️ DARVO Analysis No DARVO patterns detected. The article maintains professional technical communication standards, acknowledges challenges transparently (React 19 revert, compatibility issues), and provides constructive solutions without defensive rhetoric or victim/offender dynamics. ## 🎯 Conclusion WordPress 7.0's launch in May 2026 set the stage for significant architectural changes that June's updates began to implement. Client-side media processing, collaborative editing advancement, and development tooling consolidation represent major platform evolution toward more sophisticated, browser-based capabilities. The React 19 compatibility challenges demonstrate the complexity of maintaining backwards compatibility while advancing core technologies, but the Core team's shift to incremental migration strategy shows adaptive problem-solving. For developers, the key action items involve testing new media processing capabilities, preparing for React 19 eventual migration, and transitioning to Playground CLI for local development. These changes position WordPress for more dynamic, collaborative, and efficient development workflows while maintaining the platform's commitment to accessibility and international support through Unicode email proposals and continued accessibility improvements. ## 🔄 Refactor Appendix — What's new for developers? (June 2026) ### 📚 Literature Atoms (H3) #### Client-side media processing shifts image operations from server to browser > [!quote] ID:rw_client_media > The feature uses a VIPS/WASM pipeline to generate image sub-sizes in the browser when possible, while falling back to server-side processing when needed. **Context & use**: - Active in Chromium browsers with latest Gutenberg plugin - Intelligent fallbacks for device constraints and connection speeds - Affects plugins handling uploads, metadata, thumbnails, and newer image formats **Tags**: #xref #performance-optimization **Highlight**: [view highlight](readwise://open.readwise.io/articles/wordpress-dev-june-2026#client-media) <!-- atomicity: 1 idea ✓ --> #### React 19 upgrade requires incremental strategy due to runtime conflicts > [!quote] ID:rw_react19 > Several plugins bundled React 18 JSX runtime helpers and crashed when loaded alongside React 19. The Core team plans to keep working toward React 19 for WordPress 7.1, but with a more incremental strategy. **Context & use**: - Temporary revert implemented due to plugin incompatibilities - Affects plugins using @wordpress/element or compiled JSX - Migration strategy focuses on render(), hydrate(), unmountComponentAtNode() changes **Tags**: #xref #compatibility **Highlight**: [view highlight](readwise://open.readwise.io/articles/wordpress-dev-june-2026#react19) <!-- atomicity: 1 idea ✓ --> #### Playground CLI replaces wp-now for local WordPress development > [!quote] ID:rw_playground_cli > wp-now is deprecated. If you still use wp-now for quick local WordPress environments, it is time to move to the Playground CLI. **Context & use**: - Official recommendation for local development workflows - Supports saved sites with persistence across sessions - Enables PR previews and runnable PHP documentation examples **Tags**: #developer-tools #xref **Highlight**: [view highlight](readwise://open.readwise.io/articles/wordpress-dev-june-2026#playground-cli) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### Browser-based processing reduces server dependency for media operations **Claim**: Client-side media processing using WebAssembly can handle image transformations locally while maintaining server fallbacks for compatibility and resource constraints. **Evidence pointer**: [[#Client-side media processing shifts image operations from server to browser]] **Scope & conditions**: Effective on modern browsers with sufficient RAM and permissive CSP; requires careful fallback implementation for universal compatibility **Links**: - [[Performance optimization]] — because extends by reducing server computational load - [[Progressive enhancement]] — because applies-in media processing workflows - [[WebAssembly capabilities]] — because evidence-for browser-native processing viability <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - Test client-side media processing with AVIF/WebP images on low-memory devices — https://make.wordpress.org/test/2026/06/01/client-side-media-processing-call-for-testing/ #fleeting #inbox - Audit plugin JSX runtime dependencies before React 19 re-migration — https://make.wordpress.org/core/2026/04/15/react-19-upgrade-dev-note/ #fleeting #inbox - Migrate local development setup from wp-now to Playground CLI — https://wordpress.github.io/wordpress-playground/docs/playground-cli/ #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Update local WordPress development workflow to use Playground CLI instead of wp-now — developer productivity #things - [ ] Review plugin codebase for React 18 JSX runtime dependencies and prepare migration plan — compatibility audit #things <!-- deep-read:sections end --> ## Highlights - The feature uses a VIPS/WASM pipeline to generate image sub-sizes in the browser when possible, while falling back to server-side processing when needed. - Note: 📚 Client-side media processing shifts image operations from server to browser · - Active in Chromium browsers with latest Gutenberg plugin - Intelligent fallbacks for device constraints and connection speeds - Affects plugins handling uploads, metadata, thumbnails, and newer image formats · #atom/literature/h1 - Several plugins bundled React 18 JSX runtime helpers and crashed when loaded alongside React 19. The Core team plans to keep working toward React 19 for WordPress 7.1, but with a more incremental strategy. - Note: 📚 React 19 upgrade requires incremental strategy due to runtime conflicts · - Temporary revert implemented due to plugin incompatibilities - Affects plugins using @wordpress/element or compiled JSX - Migration strategy focuses on render(), hydrate(), unmountComponentAtNode() changes · #atom/literature/h2 - wp-now is deprecated. If you still use wp-now for quick local WordPress environments, it is time to move to the Playground CLI. - Note: 📚 Playground CLI replaces wp-now for local WordPress development · - Official recommendation for local development workflows - Supports saved sites with persistence across sessions - Enables PR previews and runnable PHP documentation examples · #atom/literature/h3 - Browser-based processing reduces server dependency for media operations - Note: [[Performance optimization]] — because extends by reducing server computational load · - [[Performance optimization]] — because extends by reducing server computational load · #atom/zettel/z1 - Test client-side media processing with AVIF/WebP images on low-memory devices — https://make.wordpress.org/test/2026/06/01/client-side-media-processing-call-for-testing/ - Note: ✏️ Fleeting capture #atom/fleeting/f1 - Audit plugin JSX runtime dependencies before React 19 re-migration — https://make.wordpress.org/core/2026/04/15/react-19-upgrade-dev-note/ - Note: ✏️ Fleeting capture #atom/fleeting/f2 - Migrate local development setup from wp-now to Playground CLI — https://wordpress.github.io/wordpress-playground/docs/playground-cli/ - Note: ✏️ Fleeting capture #atom/fleeting/f3