ACF Field Key Generator
Generate Advanced Custom Fields keys in the format ACF uses: group_ and field_ followed by a 13-character hex suffix. Make one or many at once and copy them. Everything runs in your browser.
crypto.getRandomValues. Nothing is uploaded or stored.About the ACF Field Key Generator
The ACF Field Key Generator creates Advanced Custom Fields keys in the exact format ACF uses: a group key looks like group_ followed by a 13-character hex suffix, and a field key looks like field_ followed by the same style of suffix. Pick the key type, set how many you want, and generate them in one click. It is built for WordPress developers who register field groups in PHP or hand-edit ACF JSON and need fresh, unique keys. Everything runs in your browser with crypto.getRandomValues, so nothing is uploaded or stored.
How it works
- Choose the key type: Field for field_ keys, or Group for group_ keys.
- Set the count to generate one key or a batch at once.
- Click Generate. Each key gets a unique 13-character hex suffix.
- Click Copy to copy all generated keys to your clipboard.
Features
- Generates both field_ and group_ keys in ACF's format.
- Batch generation: make up to 200 keys in one click.
- Random suffix from crypto.getRandomValues, so keys do not collide in practice.
- One-click copy of all generated keys.
- Runs fully client-side. No accounts, no network calls, no logging.
Frequently asked questions
What format do ACF keys use?
A group key is group_ followed by a 13-character lowercase hex suffix, and a field key is field_ followed by the same kind of suffix. This tool matches that pattern so the keys drop straight into ACF JSON or PHP field registration.
Are the generated keys unique?
Each suffix comes from crypto.getRandomValues, giving a large random space. Collisions are not a practical concern for normal use. If you generate a large batch, you can still scan the list to confirm.
Where do I use these keys?
Use them as the 'key' value when registering fields and field groups with acf_add_local_field_group, in exported ACF JSON, or when hand-writing field definitions. The key is what ACF uses internally to link a field to its stored meta.
Can I change a key after data is saved?
Avoid it. ACF ties saved post meta to the field key, so changing a key after values exist can orphan that data. Generate the key once, then keep it the same across environments when you migrate a field group.
Is my data sent anywhere?
No. Keys are generated entirely in your browser. There is no server call, no storage, and no tracking of what you create.