Important updates in the 3.0.0 release (3.0.x branch)

Since Drupal 10.1.0, limiting the text formats per field instance is a feature provided by Drupal core. Read https://www.drupal.org/node/3318572 for details.
In the 3.0.0 release, the allowed formats feature has been removed as obsolete, but we provide an update path from existing sites to move the allowed formats, as they were stored by the previous versions of the module, to Drupal >=10.1.0 way, in field settings.
The module provides also a feature that allows site builders to hide the formatted text format help and guidelines. Even this feature is still preserved in the 3.0.x module branch, there is an issue that aims to move it in Drupal core in the future. See https://www.drupal.org/i/3323007.

What you need to do?

When your site is upgrading to Drupal 10.1, install also the 3.0.0 release of the module.
Running database updates will move the allowed formats from module's third-party settings to the field config settings.
Now it's time to re-export your configuration in the config sync directory, in order to update the affected YAML files.

Legacy 2.0.x functionality

Limit which text formats are available for each field instance and improve usability by hiding often confusing options like the text format selection, the "about text formats" link and associated guidelines. You will find a set of checkboxes for the field settings (not the widget settings on the form display tab) of text fields.

Note that base fields defined by the entity type (for example the description field of taxonomy terms) cannot have their allowed formats limited through the UI.

If you use this module and would prefer if this functionality was built-in, please get involved in the original issue for Drupal core: #784672: Allow text field to enforce a specific text format

RTBC issues for Allowed Formats

Filters