Title: Changing custom fields type
Last modified: August 24, 2016

---

# Changing custom fields type

 *  Resolved [Kermit524](https://wordpress.org/support/users/kermit524/)
 * (@kermit524)
 * [11 years ago](https://wordpress.org/support/topic/changing-custom-fields-type/)
 * Hi,
    I have created a multiline custom field, but need to change its type to 
   wysiwyg. Couldn’t find a way to edit the type, so I tried to delete and recreate
   it, but I get an error message stating the field name and slugs already exists.
   I tried to google for a solution but couldn’t find anything on the net. Many 
   thanks in advance, Michal
 * [https://wordpress.org/plugins/types/](https://wordpress.org/plugins/types/)

Viewing 1 replies (of 1 total)

 *  [Marcin Pietrzak](https://wordpress.org/support/users/iworks/)
 * (@iworks)
 * [11 years ago](https://wordpress.org/support/topic/changing-custom-fields-type/#post-6143149)
 * Dear Kermit524
 * Here you have explanation how to change field type:
 * [http://wp-types.com/faq/how-do-i-convert-existing-custom-types-and-fields-to-types-control/](http://wp-types.com/faq/how-do-i-convert-existing-custom-types-and-fields-to-types-control/)
 * Cheers,
    Marcin

Viewing 1 replies (of 1 total)

The topic ‘Changing custom fields type’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/types_ced1d3.svg)
 * [Toolset Types - Custom Post Types, Custom Fields and Taxonomies](https://wordpress.org/plugins/types/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/types/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/types/)
 * [Active Topics](https://wordpress.org/support/plugin/types/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/types/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/types/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Marcin Pietrzak](https://wordpress.org/support/users/iworks/)
 * Last activity: [11 years ago](https://wordpress.org/support/topic/changing-custom-fields-type/#post-6143149)
 * Status: resolved