Title: Fieldstone – Custom Fields, Post Types & Custom Table Storage Author: fieldstonewp Published: July 19, 2026 Last modified: September 29, 2026 --- Search plugins ![](https://ps.w.org/fieldstone/assets/banner-772x250.png?rev=3719669) ![](https://ps.w.org/fieldstone/assets/icon.svg?rev=3707832) # Fieldstone – Custom Fields, Post Types & Custom Table Storage By [fieldstonewp](https://profiles.wordpress.org/fieldstonewp/) [Download](https://downloads.wordpress.org/plugin/fieldstone.1.3.1.zip) * [Details](https://kal.wordpress.org/plugins/fieldstone/#description) * [Reviews](https://kal.wordpress.org/plugins/fieldstone/#reviews) * [Installation](https://kal.wordpress.org/plugins/fieldstone/#installation) * [Development](https://kal.wordpress.org/plugins/fieldstone/#developers) [Support](https://wordpress.org/support/plugin/fieldstone/) ## Description Fieldstone is a content-modeling plugin for WordPress: build field groups, custom post types and taxonomies from a clean visual editor, then read the values in your theme with simple template functions. What makes Fieldstone different is **where your data lives**. Field values are stored in dedicated, indexed database tables — one row per post — instead of scattering several rows per field across `wp_postmeta`. That means faster queries and no postmeta bloat. A **postmeta mirror (on by default)** keeps a plain copy of every value where the rest of the ecosystem expects it, so your SEO, backup, export and search plugins keep working untouched. **Already using Advanced Custom Fields?** Fieldstone imports your ACF field groups in one click, warns in plain English about anything that can’t map one-to-one, and leaves your ACF data untouched so you can run both side by side while you check. The template API is familiar too — `fstn_get_field()` and `fstn_the_field()` work the way you’d expect. #### Why developers choose Fieldstone * **Custom-table storage** — one indexed row per post, not several rows per field in postmeta. * **24 free field types** — from text and select to image, WYSIWYG, oEmbed, link and icon picker. * **One-click import from ACF** — deterministic mapping, plain-English warnings, your data untouched. * **Front-end forms** — `fstn_form()` with validation, a honeypot and rate limiting. * **Built for deployments** — Local JSON, WP-CLI and a REST API. * **Your data stays on uninstall** — nothing is deleted unless you opt in. **Try it before you install** — click **Live Preview** above to open Fieldstone in a sandboxed WordPress right in your browser. #### Features * **Visual field group editor** — 24 field types: text, textarea, number, range, email, URL, password, select, checkbox, radio, button group, true/false, image, file, WYSIWYG, oEmbed, date, colour, link, icon picker, post link, and the layout types tab, accordion and message. * **Custom table storage** — one indexed row per post; opt any field into a real database index. * **Postmeta mirror** — full compatibility with WordPress export/import, backup plugins, SEO variables, and search plugins. A rebuild tool covers both directions. * **Location rules** — target field groups by post type, page template, specific post/page, page type (front page, child pages…), post status, user role, taxonomy, attachment type, or menu item, combined with and/or logic. * **Fields wherever the content is** — post screens, user profiles, taxonomy terms, attachments (including the media modal), and navigation menu items. * **Screen settings per group** — put a group below the editor, above it, or in the side column; go seamless; place labels beside fields; choose where help text sits; order groups; hide WordPress panels you do not want; switch a group off without losing its data. * **Front-end forms** — `fstn_form()` renders a group on the front of the site and accepts the submission, with validation, a honeypot and rate limiting. What the form targets is stored on the server, never in the page, so a submission cannot be edited into writing somewhere else. * **Shortcode** — `[fieldstone field="subtitle"]` prints a value anywhere, always escaped. * **Duplicate, import and export** — copy a group or a single field; export groups as JSON or as PHP that registers them from a file; import a JSON export back. * **Conditional logic** — show or hide fields based on other fields’ values, enforced server-side. * **Validation** — mark any field required, and set length, range, pattern or format rules with your own error message. Checked in the browser before saving and re- checked on the server, where an invalid field is reported without overwriting the value you already had. * **Import from Advanced Custom Fields** — bring your existing ACF field groups across in one click, with a plain-English warning for anything that can’t map one to one. Deterministic mapping, no AI involved, and your ACF data is left untouched. * **Custom post types & taxonomies** — register them from the same editor, with labels generated for you. * **Local JSON** — every definition (field groups, post types, taxonomies) syncs to files in your theme for version control and deployments. * **REST API** — opt field groups into the REST API; values appear on post responses and are writable with proper permissions. * **WP-CLI** — `wp fstn json status|sync`, `wp fstn mirror rebuild`, `wp fstn table status`. * **Developer API** — `fstn_get_field()`, `fstn_the_field()` (escaped by default),` fstn_update_field()`, `fstn_register_field_group()`, and a stable extension contract for custom field types. * **Generate with AI (optional)** — describe a field group in plain language (“ a recipe with ingredients, prep time and a photo”) and get the whole group drafted for review: correct types, choices, validation rules, and a location rule. Or open a group you have already started and ask for the fields it is **missing**— suggestions are added for review and never rename or replace what you built. Bring-your-own Anthropic API key; completely off until you add one. See “External services” below. #### Free vs Pro Fieldstone is fully functional on its own — the free plugin above is everything you need to model content and read it in your theme. **Fieldstone Pro** is an optional upgrade that adds the advanced, repeatable and relational field types, all with the same fast custom-table storage, plus automatic updates and priority support. **Website:** [https://fieldstonewp.com/](https://fieldstonewp.com/) — **Plans & pricing:** [https://fieldstonewp.com/pricing/](https://fieldstonewp.com/pricing/)—** Documentation:** [https://fieldstonewp.com/docs/](https://fieldstonewp.com/docs/) **The free plugin includes:** * 24 field types (text, textarea, number, range, email, URL, password, select, checkbox, radio, button group, true/false, image, file, WYSIWYG, oEmbed, date, colour, link, icon picker, post link, tab, accordion and message) * Custom-table storage with the postmeta mirror * Location rules, screen settings, conditional logic and validation * Front-end forms, shortcode, REST API, WP-CLI and Local JSON * Import from Advanced Custom Fields * Optional AI field-group generation (bring your own key) **Fieldstone Pro adds:** * **Repeater** — unlimited repeatable rows of sub-fields, stored in their own table * **Flexible Content** — layout blocks editors can add, reorder and mix freely * **Group** — bundle (and nest) related fields as one reusable unit * **Relational fields** — Post Object, Relationship, User and Taxonomy, with two- way links * **Gallery** — ordered image galleries and richer media pickers * **Page Link, Date/Time, Time and Google Map** fields * **Clone** — reuse another group’s fields at any position * **Options pages** — site-wide settings screens using the same fields * **Block bindings** — bind core WordPress blocks to your Fieldstone fields * **Automatic updates and priority support** Plans scale from a single site to unlimited production sites. Staging and development sites are always free, and every plan comes with a 30-day money-back guarantee. See plans and pricing at https://fieldstonewp.com/pricing/. #### How to use 1. Go to **Fieldstone New Field Group**, add your fields, and set a **location rule**( e.g. _Post Type is Page_). 2. Edit a matching post — your fields appear in a metabox. Fill them in and update. 3. Display the values in your theme with the template functions below. #### Template functions * `fstn_get_field( $name, $context, $format )` — returns a field value (formatted by default). You escape the output. * `fstn_the_field( $name, $context )` — echoes the value already escaped with ` esc_html()`. Best for plain text. * `fstn_get_fields( $context )` — returns all values for an object as a `name = > value` array. * `fstn_update_field( $name, $value, $context )` — sanitizes and stores a value. * `fstn_delete_field( $name, $context )` — deletes a value. * $context defaults to the current post in The Loop. It also accepts a post ID (` 123`), `'option'` for site-wide values, `'user_5'` for a user, `'term_12'` for a term, or a `WP_Post` / `WP_User` / `WP_Term` object. #### Displaying each field type **Text / Textarea / Email** — returns a string (`''` when empty). ```

``` **URL** — returns an escaped URL string. ``` Visit ``` **Number** — returns an int (or float when decimals are enabled), `null` when empty. ``` $ ``` **True / False** — returns a bool. ``` Featured ``` **Select / Radio** — returns the chosen value as a string. A select with “Allow multiple” returns an array of strings. ```
    • ``` **Checkbox** — returns an array of the checked values. ```
    • ``` **Image** — return format is a per-field setting: `array` (default) returns `id`,` url` and `alt`; `url` returns the URL string; `id` returns the attachment ID. ``` <?php echo esc_attr( $img['alt'] ); ?> ``` With return format `id`, use core helpers for responsive images: `echo wp_get_attachment_image( fstn_get_field( 'headshot' ), 'large' );` **File** — same formats as image; the default array carries `id`, `url` and `filename`. ``` ``` **WYSIWYG** — returns formatted HTML. Print with `wp_kses_post()`. ```
    ``` **Date** — returns a string in the field’s return format (default `Y-m-d`), `null` when empty. ``` ``` **Color** — returns a hex string: `#rrggbb`, or `#rrggbbaa` when opacity is below 100%. ``` ``` **Post Link (relationship)** — returns a `WP_Post` object by default, or the post ID with return format `id`. ``` ``` #### Reading many fields at once ```

    ``` #### Options, users and terms ``` ``` ### External services #### oEmbed providers The **oEmbed field** turns a URL you paste into an embed, exactly as pasting the same URL into the post editor does. When such a field is displayed, WordPress asks that provider (YouTube, Vimeo, Spotify, X and the rest of its built-in list) for the embed markup, and caches the answer. Only the URL saved in the field is sent, and only to the provider that URL points at. If you never use an oEmbed field, no such request is ever made. #### Anthropic API Fieldstone can optionally connect to the **Anthropic API** (api.anthropic.com) to power its two AI features: “Generate with AI” and “Suggest fields”. * **What is sent, and when:** for _Generate_, only the field-group description you type into the Generate panel. For _Suggest fields_, only the title of the group you are editing and the label, name and type of the fields already in it. Both also send the plugin’s field-type instructions. A request is made only when you have saved your own Anthropic API key in Fieldstone Settings AND click the Generate or Suggest fields button. No site content, posts, field values, user data, or analytics are ever sent, and nothing is sent in the background. * **Who provides it:** the request goes directly from your server to Anthropic, PBC using your own API key — never through any Fieldstone server. Usage is billed by Anthropic to your account (typically a few cents per generation). * Anthropic [terms of service](https://www.anthropic.com/legal/commercial-terms) and [privacy policy](https://www.anthropic.com/legal/privacy). Without an API key, no AI features are shown and the plugin makes no external requests at all. ## Screenshots [⌊Field groups list — field counts, storage engine and REST status at a glance.⌉⌊ Field groups list — field counts, storage engine and REST status at a glance.⌉[ Field groups list — field counts, storage engine and REST status at a glance. [⌊One-click import from Advanced Custom Fields, with plain-English warnings.⌉⌊One- click import from Advanced Custom Fields, with plain-English warnings.⌉[ One-click import from Advanced Custom Fields, with plain-English warnings. [⌊The field group editor — fields on a 12-column grid, with per-field widths.⌉⌊The field group editor — fields on a 12-column grid, with per-field widths.⌉[ The field group editor — fields on a 12-column grid, with per-field widths. [⌊Searchable, illustrated field-type picker with 24 free field types.⌉⌊Searchable, illustrated field-type picker with 24 free field types.⌉[ Searchable, illustrated field-type picker with 24 free field types. ## Installation 1. Upload the plugin to `/wp-content/plugins/fieldstone/`, or install it through the WordPress plugins screen. 2. Activate the plugin. 3. Go to **Fieldstone** in the admin menu to create your first field group. ## FAQ ### How do I display a field in my theme? Use `fstn_the_field( 'field_name' )` for escaped plain text, or `$value = fstn_get_field(' field_name' )` when you need the raw formatted value (arrays for checkboxes, `WP_Post` for post links, and so on). See the _Displaying each field type_ section in the Description for a complete example per field type. ### Is there full documentation? Yes. Complete documentation for both the free plugin and Fieldstone Pro — covering every field type (how to add and configure it, what it stores, and how to display it in a theme), the template-function reference, Pro loop and relationship guides, and advanced topics — is at [https://fieldstonewp.com/docs/](https://fieldstonewp.com/docs/). ### Does the AI feature cost money or send my data anywhere? The AI features are optional and off by default. They use your own Anthropic API key (pay-as-you-go with Anthropic, typically a few cents per request) and send only the description you type, or — when asking for missing fields — the title and field list of the group you are editing. The request goes directly to api.anthropic.com, never through any Fieldstone server, and your posts and field values are never sent. Tip: create a dedicated API key with a monthly spend limit. See the “External services” section for details. ### Can I move my field groups over from Advanced Custom Fields? Yes. With ACF active, an import banner appears on the Fieldstone field-groups screen listing your ACF groups. Importing recreates a group as a Fieldstone definition and creates its storage table; anything that has no equivalent in the free build is reported as a warning rather than silently dropped. Your ACF groups and their data are left exactly as they were, so you can run both while you check the result. ### Where is my data stored? Field values live in dedicated tables (one per field group, one row per post). By default every value is also mirrored into postmeta so other plugins can see it. Turning the mirror off is possible in Settings, but it will hide Fieldstone data from plugins that read postmeta. ### Does deleting the plugin remove my data? No. By default all data is kept. There is an explicit opt-in setting (“Remove all data on uninstall”) if you want a full cleanup. ### Can I version-control my field definitions? Yes. Create a `fieldstone-json` folder inside your uploads directory (`wp-content/ uploads/fieldstone-json`) and every save writes the definition there as JSON (the folder is protected from direct web access). Definitions in that folder load with priority and can be synced with `wp fstn json sync`. ### Is it multisite compatible? Fieldstone works on individual sites in a multisite network. There is no network- level UI yet. ### Is there a Pro version? Yes. Fieldstone Pro adds the advanced field types — Repeater, Flexible Content, Group, relational fields (Post Object, Relationship, User, Taxonomy), Gallery, Clone, Options pages, block bindings and more — all with the same custom-table storage, plus automatic updates and support. The free plugin is fully functional without it. See the “Free vs Pro” section above, or plans and pricing at https://fieldstonewp. com/pricing/. ### Will my SEO, backup and search plugins see Fieldstone data? Yes. A postmeta mirror is on by default, so every value is also written to `wp_postmeta` where the rest of the WordPress ecosystem expects it — SEO variables, backups, exports and search plugins keep working. If you ever need to rebuild the mirror in either direction, use **Fieldstone Tools** or `wp fstn mirror rebuild`. ### Can I use Fieldstone with Elementor, Bricks or other page builders? Fieldstone does not ship native page-builder integrations. Because the postmeta mirror is on by default, your Fieldstone values are available through standard custom- field/postmeta lookups, and you can always output them with the template functions(` fstn_get_field()`) or the `[fieldstone field="…"]` shortcode. ### Can I run Fieldstone and ACF at the same time? Yes — that is how migration works. Keep Advanced Custom Fields active, import your groups into Fieldstone, and check the result before switching. Fieldstone’s template functions use the `fstn_` prefix (`fstn_get_field()`, `fstn_the_field()`), so they do not collide with ACF’s functions and both can run side by side. ### Is Fieldstone free for commercial and client sites? Yes. Fieldstone is free and open source under the GPLv2 (or later), so you can use it on unlimited personal, commercial and client sites at no cost. Fieldstone Pro is an optional paid upgrade for the advanced field types. ### How do I get help? Ask in the [support forum](https://wordpress.org/support/plugin/fieldstone/), and see the full documentation at [https://fieldstonewp.com/docs/](https://fieldstonewp.com/docs/). ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Fieldstone – Custom Fields, Post Types & Custom Table Storage” is open source software. The following people have contributed to this plugin. Contributors * [ fieldstonewp ](https://profiles.wordpress.org/fieldstonewp/) [Translate “Fieldstone – Custom Fields, Post Types & Custom Table Storage” into your language.](https://translate.wordpress.org/projects/wp-plugins/fieldstone) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/fieldstone/), check out the [SVN repository](https://plugins.svn.wordpress.org/fieldstone/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/fieldstone/) by [RSS](https://plugins.trac.wordpress.org/log/fieldstone/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.3.1 * New: an “Upgrade to Pro” screen under the Fieldstone menu, so you can see what the Pro field types add and where to get them. * Fixed: date, time and date-time fields are now the same height as the inputs beside them. The browser draws its own editable innards for these, and they were sitting six pixels proud of everything else on the row. * Fixed: a value column whose type no longer matches its field is corrected the next time the group is saved. Until now only a change to the field itself triggered a migration, so a column left wrong by an earlier version stayed wrong. #### 1.3.0 * New: nine more field types — range, password, button group, oEmbed, icon picker, link (URL, text and target in one field), and the layout types tab, accordion and message. 24 in total. * New: fields on user profiles, taxonomy terms, attachments (including inside the media modal) and navigation menu items, with location rules to match. * New: front-end forms. `fstn_form()` renders a field group on the front of your site and accepts the submission — create a post or edit an existing one, with validation, a honeypot and rate limiting for logged-out visitors. What a form targets is stored on the server and never in the page, so a submission cannot be edited into writing somewhere else. * New: `[fieldstone field="subtitle"]` shortcode. Output is always escaped; there is no attribute to turn that off. * New: per-field help text, and a choice of whether it sits under the label or under the field. * New: group screen settings — position (below the editor, above it, or in the side column), seamless style, labels beside fields, menu order, hiding WordPress panels, a description, and an active switch that keeps a group’s data while taking it off every screen. * New: duplicate a field group or a single field; a Tools screen that exports groups as JSON or as PHP and imports a JSON export back. * Improved: the ACF importer brings across tabs, accordions, messages, links, sliders and icon pickers instead of skipping them or flattening them to a plainer type, and it carries a group’s screen settings and help text with it. * New: tabs can be placed along the top or down the left, and a tab can start a second group of tabs rather than joining the row above it. * Improved: every field type redrawn. Fields sit on a twelve-column grid with a per-field width, so short fields can share a row; repeater and flexible-content rows fold up with a summary of what is in them; the field-type picker is searchable, grouped and illustrated; and each field’s settings are split across General, Validation, Presentation and Conditional Logic instead of one long list. * Improved: the link field opens WordPress’s own link dialog — address, link text,“ open in a new tab”, and a search over your existing posts and pages. * Improved: the field group editor is one column. Fields take the full width, and location rules, presentation and group settings share a Settings card at the bottom. Each field row carries Edit, Duplicate, Move and Delete, sub-fields included. * Fixed: two fields with the same name — two tabs called General, or a `title` field in two different groups — no longer silently vanish on save. Field keys are unique to their group now, and an existing key is never written over. * Fixed: Update on a post could do nothing at all when a group contained a link field. The pre-save check can no longer swallow a submission, whatever it hits. * Fixed: saving a field group keeps you on it instead of returning to the list. * Fixed: a field group containing a layout field no longer produces a database error on save. * Note: the oEmbed field asks the provider you link to for its embed markup. See“ External services”. #### 1.2.0 * New: field validation — a “Required” toggle on every field, plus length, range, pattern and format rules with your own message. Validation runs before the browser submits and again on the server; an invalid field is reported and its previously saved value is kept rather than overwritten, and valid fields in the same group still save. * New: import from Advanced Custom Fields — recreate your ACF field groups in one click, with per-group warnings for anything that cannot map exactly. Deterministic mapping (no AI), and your ACF groups and data are left untouched. * New: “Suggest fields” — with an API key saved, ask what an in-progress field group is missing. Suggestions are appended for review and can never rename or overwrite fields you already created. * Improved: AI generation now knows the plugin’s real field types and can set validation rules on the fields it drafts. * Fixed: the field-editing scripts (conditional logic, media and colour pickers) can now be loaded on screens other than the post editor. #### 1.1.0 * New: Generate with AI (optional, bring-your-own Anthropic API key) — describe a field group in plain language and get the whole group drafted for review before saving. * New: premium admin design — branded header, segmented tabs, colored field-type badges, refined cards, inputs, and settings screen. * The AI feature is entirely opt-in: without an API key nothing is shown and no external requests are made. #### 1.0.0 * Initial release: field groups with 15 field types, custom-table storage with postmeta mirror, conditional logic, custom post types & taxonomies, Local JSON sync, REST API exposure, WP-CLI commands, WXR import bridge. ## Meta * Version **1.3.1** * Last updated **4 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1.2** * PHP version ** 8.0 or higher ** * Language * [English (US)](https://wordpress.org/plugins/fieldstone/) * Tags * [custom fields](https://kal.wordpress.org/plugins/tags/custom-fields/)[custom post types](https://kal.wordpress.org/plugins/tags/custom-post-types/) [custom table](https://kal.wordpress.org/plugins/tags/custom-table/)[field group](https://kal.wordpress.org/plugins/tags/field-group/) [taxonomies](https://kal.wordpress.org/plugins/tags/taxonomies/) * [Advanced View](https://kal.wordpress.org/plugins/fieldstone/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/fieldstone/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/fieldstone/reviews/) ## Contributors * [ fieldstonewp ](https://profiles.wordpress.org/fieldstonewp/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/fieldstone/)