Start with existing content
In WordPress, open Validated Field → WordPress tables. Choose Posts, Pages or a custom post type, then select ACF fields from the labeled checkboxes. Field names appear next to their labels; the original ACF keys remain the saved identifiers. Each field must be a top-level field in an active group that applies to the entire post type. Conditional field groups and duplicate field names are rejected.
Selected ACF columns appear alongside the native WordPress columns. Use Open table workspace for the Validated Field table. Public visibility, native editing, original ACF field keys and storage stay in place. Removing the table settings preserves content and values.
Free includes scalar text, numeric and boolean inline editing, validated Quick Add, personal column visibility/order/widths and sticky headers. Table writes use the same validation and permission checks as record forms. A changed record version must be reloaded before an older table edit can overwrite it.
Advanced queries in Pro
Pro adds ordered multi-column sorting, choice-label and authorized relationship-name sorting, nested AND/OR filters, relative-date presets and filtered sum, average, minimum, maximum and count metrics. Metrics cover the authorized matching set before pagination. Queries have separate limits of 10,000 authorized rows and 10,000 processing-work entries. Work includes rejected source records, Index candidates and relationship display values. A query can reach the work limit before 10,000 authorized rows; a capacity error returns no partial rows or metrics. These limits bound application processing, not database engine work or the size of one ACF record.
Saved/shared views never grant access to records or fields. ACF Pro field types require ACF Pro independently of the Validated Field edition.
Background tools in Pro
Preview selected records or all matching results before starting bulk work. Set or clear fields, transform text, adjust numbers, or add/remove list and relationship entries. Jobs recheck permissions and record versions, report individual failures and support cancellation between batches. Recovery creates another preview and refuses to overwrite later edits.
Background exports offer raw/formatted values and owner-only profiles. Downloads recheck access and have no public file URL. Quality scans report invalid/missing values, broken references and duplicate scalar values without editing records. Every current field must be readable. Hidden fields added after preview and later access changes block the scan or its retained results without exposing field names; readable additions are included.
Each job snapshots at most 2,000 rows and processes 20 per batch. CSV is capped at 5 MiB and stored state at 8 MiB. A site retains at most 100 snapshots for 24 hours; export profiles are limited to 100 per actor. WordPress job cron must run to process queued work. Deactivation parks work for administrator review; expired snapshots cannot resume. Content and audit history are preserved.
Native editing boundaries
Ordinary WordPress editors and third-party integrations retain their own write behavior. Enabling a table does not make every direct PHP or SQL write transactional and does not make public content private. Use managed objects when your records need the application’s private data boundary.
This documentation describes the unreleased development build. See the changelog and Free/Pro comparison.