plugin.new
Summary
Writing a WordPress plugin from scratch means context-switching between the plugin handbook, Stack Overflow, and a code editor — for something that might take ten minutes if you already knew the APIs. Plugin.new is a browser-based tool that takes a text prompt and returns a working plugin zip, skipping that entire ramp.
The workflow is prompt-in, code-out: describe what you want the plugin to do, and the tool generates the file structure and logic for WordPress, Shopify, or Figma targets. Revisions happen through chat, so fixing a hook or tweaking a Shopify metafield doesn't require opening an editor. Export lands as a zip or pushes to GitHub. Where it breaks: the scraped page content is thin, so the ceiling on complexity — nested custom post types, multi-step Shopify webhooks, anything requiring external API auth — is not documented. Teams building past simple utility plugins should test that ceiling early.
Bottom line: Pick this to ship a Figma utility plugin or a WordPress shortcode in an afternoon; expect to reach outside it when the plugin needs multi-step webhooks or logic that requires more than one round of prompt revision to express correctly.
Pricing Plans
Usage-Based- Free Tier
- $0.10 of AI usage monthly until exhausted
Free
$0.10 of AI usage monthly, unlimited generations and revisions until usage runs out, 2 revisions, download as zip, community access
- $0.10 usage
- Unlimited generations
- Download as zip
Pro
$10 of AI usage monthly, unlimited access, all models, GitHub push, download as zip
- $10 usage included
- All models
- GitHub push
Agency
$30 of AI usage monthly, unlimited access, all models, GitHub push, download as zip
- $30 usage included
- All models
- GitHub push
View full pricing on plugin.new →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Generates plugin file structures targeting WordPress, Shopify, and Figma from a single interface, so teams building across platforms don't maintain separate toolchains for each ecosystem.
- Chat-based revision loop lets you adjust generated code without leaving the browser, which means a wrong hook or misnamed function gets fixed in the same session rather than dropped back into a manual edit cycle.
- GitHub export is available, so generated plugins slot into an existing deployment workflow instead of living only as downloaded zips.
- Freemium entry point with usage-based pricing means occasional plugin needs — a one-off Figma utility, a single WordPress shortcode — carry no fixed overhead for teams that don't generate plugins regularly.
Cons
Sign in to edit- The vendor page requires JavaScript to render any content, which means there is no accessible documentation to audit. Teams cannot determine the complexity ceiling — maximum plugin size, supported API surface, external auth handling — without direct testing, and that gap is a production risk before any real commitment.
- One-shot and chat-revision generation works for utility-scale plugins; when a WordPress plugin needs custom database tables, cron jobs, and an admin settings page wired together, the prompt-to-code model accumulates gaps that stack across revision rounds. At that point, teams either maintain a parallel manual codebase or switch to a general-purpose code assistant like GitHub Copilot or Cursor that can hold more context across a larger file tree.
- No API access and no self-hosted option, per the validator context, means every generation round goes through the vendor's infrastructure. Teams with code confidentiality requirements — proprietary Shopify logic, unreleased Figma plugin concepts — have no path to keeping prompts and output on-premises.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Web
- API Available
- No
- Self-Hosted
- No
- Last Updated
- 2026-07-05T02:29:51.962Z
Best For
Who it's for
- WordPress developers needing quick prototypes
- Shopify merchants extending store functionality
- Designers creating Figma plugins
- Teams requiring occasional plugin generation
- Users avoiding manual coding for extensions
What it does well
- Generate WordPress plugins from text prompts
- Create Shopify apps without coding
- Build Figma plugins via AI
- Revise existing plugin code through chat
- Export plugins as zip files or push to GitHub
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare plugin.new
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is plugin.new free?
- plugin.new has a permanent free tier alongside paid upgrades. You can keep using a baseline version indefinitely without paying.
- Is plugin.new open source?
- No — plugin.new is a closed-source tool. Source code is not publicly available.
- What platforms does plugin.new support?
- plugin.new is available on: Web.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Best plugin.new alternatives →
Curated lists that include this category
Plugin.new handles the gap between ‘I know what I want the plugin to do’ and ‘I know how to write it’ — a gap that blocks designers, merchants, and product teams who don’t live in plugin APIs daily. The core workflow is text prompt to generated plugin code, with chat-based revision to adjust behavior, and export either as a zip file for manual installation or as a GitHub push for teams with a deployment pipeline. Supported targets, per the vendor page, include WordPress, Shopify, and Figma.
The differentiating angle is platform breadth in a single tool. Most prompt-to-code generators are general-purpose; plugin.new is scoped specifically to plugin and extension formats, which means the output respects Figma’s plugin manifest structure or WordPress’s file conventions rather than generating generic JavaScript the user still has to wire up manually.
Where it fits best: prototyping a plugin concept before committing engineering time, extending a Shopify store without a developer on retainer, or generating a Figma utility that would otherwise sit on a backlog indefinitely. Where it breaks: the vendor page renders no content without JavaScript enabled, which means independent documentation of complexity limits is not available. Teams that need plugins with external OAuth flows, multi-table database writes, or Shopify webhook chains should validate the tool against a representative prompt before committing to it as a production workflow — the chat-revision loop may not carry that weight.