WordPress Core already handles 4-byte characters (such as emojis and some special Unicode symbols) in post_content, helping to avoid content truncation on sites that still use older database configurations.

It would be very useful if ACF could provide similar handling for values stored in postmeta, especially for WYSIWYG, Textarea and Text fields.

While updating database tables to utf8mb4 is the recommended long-term solution, many users are not aware of their database configuration and never access it directly. From a user perspective, content entered into an ACF WYSIWYG field is expected to behave in the same way as content entered into the standard WordPress editor.

This becomes particularly important because a user may paste a large amount of text containing a single 4-byte character and unintentionally lose everything after that point if the database cannot store it correctly.

Possible approaches could include:

Automatic detection of unsupported 4-byte characters.

Encoding or sanitization methods similar to WordPress Core.

An optional setting such as “Ensure 4-byte / emoji compatibility”.

Admin warnings when the database configuration may cause truncation.

Providing native handling within ACF would improve consistency with WordPress Core and help protect users from unexpected data loss, especially on older sites that have not yet been fully migrated to utf8mb4.