Category filter

Configuration profile to disable Auto-Correction on iOS devices

Jump To

Learn how to disable Auto-Correction on iOS devices using a configuration profile.

Auto-Correction feature on devices automatically corrects misspelled words using the keyboard dictionary for spell-check as you type. While this feature can be helpful for users in avoiding spelling errors, it may not be adequate in every business setting or keyboard usage scenario. The configuration profile explained here can be used to configure iOS devices to have the Auto-Correction feature disabled. You can deploy the configuration profile using Hexnode’s Deploy Custom Configuration feature.


The configuration profile provided below is adapted from a third-party open-source site.


This configuration profile is supported on supervised devices running iOS 8.1.3 and later.

Disable Auto-Correction

The allowAutoCorrection key is set to false in the configuration profile, which will disable both the Auto-Correction and Smart Punctuation features on the iOS device.

Smart Punctuation on iOS is a feature that automatically formats certain types of punctuation, such as quotation marks and apostrophes, as the user types. When Auto-Correction is disabled, the device will not automatically correct misspelled words as the user types, and when Smart Punctuation is disabled, the device will not automatically format these types of punctuation.

What happens at the device end?

With the deployment of the configuration profile, both the Auto-Correction and Smart Punctuation options on the iOS device will be disabled and greyed out in the Settings app under General > Keyboard. This means that the user will not be able to turn these features on or off from the device’s settings.

Use a configuration profile to disable auto-correction on iOS devices


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile on a system before executing it in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository