We publish our roadmap so you know what you’re buying into. Below is what we’re actively building, what’s queued next, what we’re considering, and what we’ve recently shipped. Vote on features you want prioritized.
In progress (shipping within 4–8 weeks)
Migration tools
- Pods importer improvements — handle Pods’ custom database tables feature properly
- Toolset Types importer — convert Toolset Types field groups to Field Forge
- Enhanced CMB2 importer — better handling of complex CMB2 container types
AI features
- AI field type suggestions — as you type a field label, AI suggests the appropriate field type (“date of birth” → date picker)
- AI field group optimization — analyze an existing field group and suggest improvements
- Multi-language AI generation — generate field groups in other languages (for Lang Forge users)
Performance
- Query builder for archives — optimize how repeater fields are loaded for archive pages
- Async field loading — lazy load field values for fields not needed on initial render
Developer tooling
- WP-CLI expansion — more commands for bulk operations on field groups
- CI/CD recipes — documented GitHub Actions and GitLab CI templates for deploying field groups
- Schema diff visualizer — better UI for comparing field group revisions
Queued (3–6 months)
New features
- Multi-site field group sharing — define field groups once, use across a WordPress multisite network
- Role-based field access — hide specific fields from specific user roles
- Field-level validation API — custom validation logic per field via PHP hooks
- Frontend field rendering helpers — pre-built templates for common field display patterns
- Import/export via REST API — migrate field groups between sites via API calls
Integrations
- Headless WordPress SDK — npm package with Field Forge types and utilities
- Gatsby source plugin — official Field Forge data source for Gatsby sites
- Next.js WordPress template — Next.js starter template with Field Forge pre-configured
- Astro integration — official Astro integration for Field Forge
Enterprise
- White-label mode — hide Field Forge branding from clients (Agency plan)
- Audit log — who changed what, when (for compliance-heavy environments)
- Bulk user permissions — role-based permissions across field groups
- Custom post type manager — visual CPT registration alongside field groups
Under consideration
Features we’re thinking about but haven’t committed to. User interest affects prioritization.
AI expansions
- AI content generation — generate sample content for custom fields during development
- AI schema documentation — auto-generate markdown docs for field groups
- AI migration assistance — interpret complex custom code and suggest Field Forge equivalents
Advanced field types
- Polygon field — draw polygons on a map
- Signature field — touch/mouse signature capture
- Rich media fields — video, audio, 3D model support
- Ranking field — drag-to-sort ordered lists
- Matrix field — table of values with custom column types
Content workflows
- Draft versions of field data — save field values as drafts before publishing
- Approval workflows — require editor approval before field changes go live
- Scheduled field updates — change field values on a schedule
- Field locking — prevent editing of specific fields after first save
Headless enhancements
- Real-time sync — WebSocket updates when WordPress content changes (for live frontends)
- Delta API — return only fields that changed since last fetch (efficient polling)
- GraphQL subscriptions — real-time GraphQL updates
Recently shipped
Version 2.3.0 (April 2026) [Major]
- SCF import tool (WordPress.org ACF fork)
- Beta/manual migration planning paths for CMB2 and Carbon Fields
- 12 built-in AI schema templates
Version 2.2.0 (March 2026)
- AI schema generation
- Schema versioning with rollback
- Auto-preload on archive pages
Version 2.1.0 (February 2026)
- TypeScript generation
- GraphQL SDL and WPGraphQL auto-registration
- Local JSON Sync bidirectional mode
Version 2.0.0 (January 2026)
- Initial public release
- 32 field types
- Custom table storage
- ACF compatibility layer
Full changelog →
How we prioritize
Our roadmap is driven by three inputs:
- What customers request most — we track feature requests from support tickets and the contact form. Popular requests move up.
- What differentiates Field Forge — features that set us apart from ACF, SCF, and other alternatives (AI, headless, custom table, schema versioning).
- What the team can ship well — we’d rather ship a polished feature later than a rushed feature now.
If something isn’t on the roadmap but is important to you, tell us. Aligned ideas often move quickly.
Vote on features
Submit a feature request →
Tell us which roadmap items matter most for your project. High-demand items get prioritized.
Ready to try Field Forge today?
Get Field Forge — from $35/year →