You became a developer to build things — not to fill out forms
You just want to test a layout, demo a feature, or check your custom fields — but first you need to manually create 20 posts with images, taxonomies, and metadata. It's demoralizing, repetitive, and you know there has to be a better way.
We built WPfaker because we lived this problem. Every new project meant the same grind — filling out form after form just to see how a template looks with real content. We knew the tooling could be better, so we built it.
0%
Less manual work
Automation reduces manual data entry work by 80%. That's time you could spend building features instead of filling in test forms.
Time to create 20 test posts
With custom fields, images & taxonomies
Industry avg: 3–5 min per record with 10–20 fields
Annual cost of manual test data
At a $75/hr developer rate
$0
wasted per year on manual test data creation
20 posts × 5 min1.7 hrs / batch
2 resets / week~175 hrs / year
With WPfaker~17 min / year
These estimates are based on industry benchmarks for form-based data entry with 10–20 fields per record. WordPress test content with custom fields, taxonomies, and images falls squarely in that range.
Source: DocuClipper — Data Entry Statistics & Benchmarks (U.S. Bureau of Labor Statistics data)
No configuration files. No CLI setup. Works in the WordPress admin you already know.
01
Install & activate
Upload the ZIP via WordPress admin, activate, and enter your license key. No configuration needed — WPfaker detects your post types and fields automatically.
Plugins → Add New → Upload ZIP → Activate
02
Hit Generate
Pick your post type, set a count, and click one button. That's it. No field mapping, no templates to configure, no CLI commands to memorize.
WPfaker → Select post type → Generate
03
Get realistic content
Posts, images, custom fields, taxonomies, and users — all created in seconds with contextually matched data. Your dev site looks production-ready.
✓ 20 posts · 12 images · 4 authors · 156 fields
Built for developers
I got tired of copy-pasting test data
Every WordPress project started the same way — manually creating posts, uploading placeholder images, filling custom fields one by one. So I built the tool I wished existed.
WPFaker understands your post types and field groups out of the box. It detects field names like company_email or hero_image and generates contextually matched data — no configuration needed.
113
Detection types
815+
Field patterns
19
CPT domains
13
Languages
Works with
ACF Free & Pro
ACF Extended Free & Pro
JetEngine
Meta Box, MB Pro & AIO
Custom Post Type UI
ACPT
register_post_type()
Without the right tools
What stays the same if nothing changes?
Broken layouts go unnoticed.
Without realistic content, edge cases hide in plain sight. Truncated titles, empty fields, missing images — your client sees them first, not you.
Hours lost to manual entry.
Every sprint, every project — the same grind. Creating test posts by hand, uploading dummy images, copying placeholder text. It adds up to weeks per year.
Unrealistic data, wrong decisions.
"Test User 1" and Lorem Ipsum don't reveal real-world problems. You end up designing for placeholder content — then fixing layouts when actual data arrives.
With WPfaker
What your workflow looks like after
Ship with confidence.
Realistic content catches layout issues before your client does. Truncated titles, overflowing fields, missing images — you see them first, not in production.
Save hours per project.
One click replaces days of manual work. Pick your post type, hit generate — posts, images, custom fields, and taxonomies appear in seconds.
Impress clients from day one.
Presentations with real-looking content sell themselves. Realistic names, images, and addresses make your work look finished — no disclaimers needed.
Capabilities
Everything your testing workflow needs
Built on FakerPHP with deep WordPress integration. WPfaker understands your post types, field groups, and taxonomies out of the box.
Posts & Pages
Any post type. Realistic content.
Generate posts, pages, and custom post types with configurable status, featured images, excerpt, and taxonomy assignments. Auto-create authors and categories on the fly. Supports Draft, Pending, Private, Scheduled, and Published states.
Up to 500 posts per request — auto-adapts to your server
Auto-create up to 20 authors
Featured images via Unsplash, Picsum, Pexels, Pixabay, or Placeholder
Smart field detection recognizes your custom fields automatically — names, addresses, emails, prices, coordinates, dates, and more. Supports Repeater fields, Relation fields, Google Maps fields, and Galleries. Images are physically downloaded to your Media Library.
ACF Free & Pro — Repeaters, Flexible Content, Galleries
ACF Extended Free & Pro
JetEngine, Meta Box, CPTUI, ACPT
Relation, Google Maps & complex field types
Images downloaded to Media Library, not just linked
Native WordPress register_post_meta() support
For Plugin Developers
All hooks & filters. Zero shortcuts.
WPfaker uses wp_insert_post(), wp_set_object_terms(), and the full WordPress API to create content. Every action, filter, and hook fires exactly like a real user interaction — perfect for testing your plugin logic against realistic data.
All WordPress hooks & filters triggered
No direct database writes
Test your plugin with realistic content
Works with any registered post type or taxonomy — whether from your plugin, a theme, or any other method
Trusted by developers building with WordPress
113 detection types, 815+ patterns·13 languages·Up to 500 posts per batch·Full REST API
Template System
Save, reuse & share generation templates
Templates are entirely optional — WPfaker works great without them. But when you want fine-grained control, the tabbed template editor lets you define exactly how each field should be populated. Save templates, set defaults per post type, and duplicate them for quick variations.
Tabbed editor
Five focused tabs — general, core fields, custom fields, taxonomies, related CPTs
Field modes
None, Choose, or Create — per field
Defaults & duplicates
Set a default per post type, duplicate for variants
Field search
Find fields by name across large field groups
Per-field configuration
Core fields, custom fields, and taxonomies in separate tabs
Comment settings
Auto-comments, threading, and reply probability stored per template
Hierarchical categories, flat tags, and custom taxonomies. Control nesting depth (1–5 levels), breadth per level, and parent assignment. Custom fields on terms are supported too.
Users & Authors
Up to 50 users per request with locale-specific names, emails (@example.com), bios, and role assignment. Portrait photos from Unsplash as profile pictures. Administrator role excluded by default.
Comments
Threaded comments with configurable reply depth, anonymous vs registered author mix, and adjustable pending ratio. Profile pictures for a configurable percentage of commenters. Settings persist in templates.
Content Variation
Four profiles — Random, Minimal, Partial, Complete — control how densely fields are populated. The first generated post always gets Complete profile as a reference example.
Every generated item is tracked in a dedicated table. Filter by type, view metadata, and bulk-delete only WPfaker-created content. Optionally clear history on deactivation.
Image Providers
Six built-in providers: Picsum and Placeholder.com work without an API key. Unsplash, Pexels, Pixabay, and LoremFlickr add category-based photos with a free API key. 16 categories including portraits, configurable dimensions, and media library reuse.
REST API
Full REST API for posts, terms, users, templates, settings, and history. Automate generation from external tools, CI pipelines, or batch scripts. Nonce-authenticated. Safe defaults: @example.com emails, no admin role by default.
Smart Detection
Your field names tell us what to generate
WPfaker reads your custom field names and automatically determines the right content type. No manual mapping needed — a field called email_address gets a valid email, not Lorem Ipsum.
Field NameGenerated ValueConfidence
first_name
First NameJames
98%
email_address
Emailjames.wilson@example.com
99%
street_address
Street742 Evergreen Terrace
95%
unit_price
Price$1,249.00
97%
phone_number
Phone(555) 867-5309
96%
profile_photo
Image↓ portrait_08.jpg
92%
Without field detection
first_name→Lorem ipsum dolor sit
email_address→Sed ut perspiciatis
With WPfaker detection
first_name→James
email_address→james.wilson@example.com
Working with 13 locales
ENDEFRESITPTNLPLRUJAZHKOAR
Smart Detection
Deep pattern matching — no AI needed, but available if you want it
Most fields are recognized instantly by name — no external services, no API keys, no setup. For the rare cases pattern matching can't handle, you can optionally enable AI detection. But most users never need it.
113
Detection Types
Distinct content categories the system recognizes — from names and emails to coordinates, opening hours, and coupon codes. Each type knows exactly what realistic data looks like.
first_nameemailphonepricestreet_addresscitycoordinatesopening_hourscoupon_codecaloriesvideo_urlcompanyjob_titlebirth_dateskuingredientsepisode_numbertranscriptbooking_urlsubtitleservingsparkingdiscountduration+89 more
815+
Regex Patterns
Every type is matched by patterns in up to 13 languages. A field called vorname, prénom, or nombre all resolve to first_name.
first_name
ENfirst_name
DEvorname
FRprénom
ESnombre
ITnome
NLvoornaam
PLimię
JA名前
ZH名字
···4 more locales
19
CPT Domains
Context changes everything. The same field name produces different content depending on your post type — a "name" field generates the right kind of name.
field: name
RestaurantBella Italia
Team MemberSarah Mitchell
PartnerAcme Corp
producteventjobservicemediacouponeducation+9 more
1
Pattern matching first
815+ built-in regex patterns across 113 detection types handle names, addresses, emails, phones, prices, dates and more — no AI call needed.
2
Optional AI for edge cases
If you enable AI detection, fields that don't match a pattern get analyzed by your own AI provider (BYOK). Detections are cached locally — each field is analyzed only once. Completely optional.
3
Powered by the Hive
When AI detects a field with high confidence, that mapping is shared with the WPFaker Hive — a collective knowledge base built by every participating installation. The next person with the same field name gets an instant match.
Google Gemini
Gemini
BYOK
OpenAI
GPT
BYOK
Anthropic
Claude
BYOK
Detection capabilities
815+Built-in patterns
113Detection types
19CPT domains
No AI needed. Pattern matching works out of the box. AI & Hive are always opt-in.
Collective Intelligence
Every install makes WPFaker smarter
The Hive is WPFaker's shared intelligence layer. Field patterns and value lists contributed by the community make detection more accurate and content more diverse — without sharing any private data.
Pattern Mining
Every time WPFaker detects a field, it learns. Patterns like company_phone → phone or hero_image → image become shared knowledge — making detection smarter for everyone.
Field mapping
*_phone
Phone98%
*_email
Email96%
hero_*
Image94%
Value Enrichment
Seed a field with 3 example values and WPFaker expands them to 80+. The community enriches value lists so your generated content becomes more diverse over time.
Volcano names
Vesuvius, Etna, Krakatoa
80+ volcanoes worldwide
Privacy First
The Hive is fully opt-in and anonymous. Only field name patterns and value lists are shared — never site URLs, content, or personally identifiable information.
Opt-in only Anonymous No PII shared No site URLs
01
Enable the Hive
One toggle in settings
02
Generate as usual
Patterns improve silently
03
Community grows
Everyone benefits
Nested Structures
Repeater fields with content that makes sense
A recipe needs ingredients, steps, and nutrition facts — not five rows of Lorem Ipsum. WPfaker reads your sub-field names and generates realistic, contextual data for every repeater row.
Field Structure
recipe_titleText
prep_timeNumber
servingsNumber
ingredientsRepeater5 rows
├─amountNumber
├─unitSelect
└─ingredientText
stepsRepeater4 rows
├─step_numberNumber
└─instructionTextarea
nutritionGroup
├─caloriesNumber
├─proteinNumber
└─carbsNumber
Generated Output
Pasta Carbonara
30 min·4 servings
Ingredients
400gSpaghetti
200gGuanciale
4Egg Yolks
100gPecorino Romano
to tasteBlack Pepper
Instructions
1.Cook spaghetti in salted boiling water until al dente
2.Cut guanciale into small strips and fry until golden and crispy
3.Whisk egg yolks with grated pecorino and cracked black pepper
4.Toss drained pasta with guanciale, fold in egg mixture off heat
520 kcal·24g Protein·58g Carbs·18g Fat
Nested Repeaters
Repeaters inside repeaters, up to any nesting depth. Each level gets contextually appropriate content based on sub-field names.
Flexible Content
Different layouts within the same flexible content field. WPfaker picks layouts randomly and populates each one correctly.
Smart Row Counts
Randomized rows per repeater instance. The first generated post always gets maximum rows for a complete reference example.
Relational Data
Connected post types? Already handled.
Real WordPress projects don't have isolated CPTs — they have networks. Properties reference Agents, Agents belong to Agencies, Listings link to Locations. WPfaker resolves these dependencies automatically in three phases.
1
Dependency Resolution
Scans all CPTs and their relational fields to build a dependency graph. Knows which post types must exist before others can reference them.
2
Ordered Creation
Creates all posts across every CPT — without relational fields first. Ensures every referenced post type has its entries available.
3
Relationship Linking
Walks the dependency graph and fills all relational fields. Every reference points to a real, existing post — no broken links.
Supported relational field types
ACF Relationship
ACF Post Object
JetEngine Relations
Meta Box Post
Template Control
Every relationship on your terms
Save relational settings as part of your template. Enable or disable auto-creation per CPT, set exact post counts, or decouple a post type entirely — so you can develop one CPT at a time without generating the whole network.
Related Post Types
AgentsRequired
8 posts·Published
Locations
5 posts·Published
Features
12 posts·Draft
Agencies
What happens
Agentsauto-create 8
1
2
3
4
5
6
7
8
Locationsauto-create 5
1
2
3
4
5
Featuresauto-create 12 as draft
1
2
3
4
5
6
7
8
9
10
11
12
Agenciesskipped
Decoupled — no auto-creation, field left empty
Per-CPT Control
Toggle auto-creation for each related post type individually. Set exact counts, post status, and whether to apply content variation.
Standalone Mode
Decouple any CPT from its relationships. Generate properties without creating agents — use existing posts or skip relations entirely.
Smart Defaults
WPfaker calculates how many related posts you need based on field cardinality. One-to-one gets 3, many-to-many gets 8. Override anytime.
Pricing
Go from hours of busywork to seconds of automation.
One plan. Everything included. No tiers, no feature gates, no per-site limits.
Beta
Beta Pricing
$149/year$199
Billed annually. Includes license key for activation.
Early adopter deal: Subscribe during the beta and keep the $149/year price for as long as your subscription stays active. If you cancel and resubscribe later, the regular $199/year price applies. We don't know how long the beta will last — this price goes away when it ends.
Unlimited WordPress sites
All features — posts, users, terms, custom fields
Custom fields — ACF, ACF Extended, JetEngine, Meta Box, CPTUI
Everything you need to know before getting started.
WPfaker works out of the box with all major WordPress custom field and custom post type plugins:
ACF (Free & Pro) and ACF Extended
JetEngine by Crocoblock
Meta Box (including MB Pro & AIO)
Custom Post Type UI
ACPT (Advanced Custom Post Types)
It also picks up any custom post type registered directly via register_post_type() — no extra configuration needed. WPfaker automatically detects your installed plugins, reads their field groups, and generates matching content. You don't have to map anything manually.
Yes — and this is one of the things WPfaker does really well. It fully supports complex, deeply nested field structures:
Repeaters with configurable row counts
Groups and nested sub-groups
Flexible Content layouts with multiple layout types
Every sub-field gets contextually appropriate content based on its name and type. For example, a repeater called team_members with sub-fields like "name", "role", and "photo" will generate realistic team profiles — not random placeholder text. The deeper the nesting, the more time WPfaker saves you.
WPfaker generates fully localized fake data in 13 languages:
This goes beyond just translating text. Names, addresses, phone numbers, dates, and even formatting conventions match the selected locale. If you're building a multilingual WordPress site or testing an internationalized theme, WPfaker gives you realistic content in every language — not just lorem ipsum with different characters.
It does — and they're not just random stock photos. WPfaker downloads high-quality, royalty-free images from Unsplash and adds them directly to your WordPress media library.
The smart part: images are contextually matched to your field names. Here's what that looks like in practice:
A field called author_photo → portrait photography
A field called hero_image → landscape/wide shots
A field called recipe_image → food photography
This means your development site looks realistic from the start — which makes design reviews, client presentations, and theme testing significantly more meaningful.
WPfaker is built as a WordPress development tool, and we recommend using it exclusively on local or staging environments. It's not designed to run alongside real content on a live site.
That said, we've built in safety nets. Every generation run is tracked in WPfaker's built-in history, so you can:
See exactly what was generated and when
Roll back an entire batch of posts, taxonomy terms, and media files
Undo everything with a single click — no database backup needed
If you accidentally run it on the wrong environment, you're covered.
WPfaker has minimal requirements and runs on any standard WordPress setup:
WordPress 5.9 or higher
PHP 8.0 or higher
An admin account (to access the WPfaker interface)
No special server extensions, no external services, no complicated setup. It works out of the box on popular managed hosts like Cloudways, SiteGround, and WP Engine — as well as local development environments like LocalWP, DDEV, Lando, or Docker.
If you subscribe during the beta, you lock in the early-supporter rate of $149/year — and you keep that price for as long as your subscription stays active. No tricks, no automatic price bumps.
Once the beta period ends, the regular price for new subscribers will be $199/year. So the earlier you get in, the more you save long-term.
Think of it as a thank-you for believing in the product early on. Your support during beta helps us shape WPfaker into the best tool it can be.
Absolutely. A single WPfaker license covers unlimited WordPress installations — whether you're running 2 client projects or 50.
You can manage all your site activations from your WPfaker account dashboard. Activate a new site, deactivate an old one, or move your license to a different environment — it's completely flexible and designed for agencies and freelancers who juggle multiple projects.
Great question — and one we get asked a lot. We're big fans of WordPress. It's the reason WPfaker exists in the first place.
But we also believe in choosing the right tool for each project. This website is a straightforward marketing site: no blog, no regularly updated content, no need for a CMS backend. For that use case, a static site generator gives us faster load times and less infrastructure to maintain.
WordPress is at its best when you need a powerful, flexible content management system — the kind of setup where editors publish content regularly, where custom post types structure your data, and where plugins extend functionality. That's exactly the scenario WPfaker is built for, and where it saves you the most time.
That said — if WordPress is the tool you know and trust, there's absolutely nothing wrong with using it for any kind of site, including a simple one-pager. The best tool is the one that works for you and your clients. We just happened to make a different choice for this particular project.
ACF
JetEngine
Meta Box
ACF Extended
CPTUI
ACPT