# Custom Placeholders for untranslatable variables **URL:** \ **Category:** Tips and Tricks\ **Created:** [September 11, 2018, 9:08pm UTC](https://community.transifex.com/t/custom-placeholders-for-untranslatable-variables/54 "2018-09-11T21:08:03Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![flafich](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/flafich/32/11_2.png) [@flafich](https://community.transifex.com/u/flafich)\ **Post date:** [September 11, 2018, 9:10pm UTC](https://community.transifex.com/t/custom-placeholders-for-untranslatable-variables/54/2 "2018-09-11T21:10:07Z")
In the [Translation checks](https://docs.transifex.com/setup/setting-translation-checks) area, there is an option to customize placeholders per file format. You can set the delimiters using custom placeholders, and all variables that appear between those delimiters would appear in the editor as placeholders. You can set warnings or error to make sure translators are preserving them in the translation box. You can refer to best practices here: > [@Best practises on setting custom placeholders (protecting \*only\* your custom text)](https://community.transifex.com/t/best-practises-on-setting-custom-placeholders-protecting-only-your-custom-text/272): > > Adding custom placeholders from the respecting modal in translation checks page can be a breeze. You can check how this is done in our docs section for [Setting Translation Checks](https://docs.transifex.com/setup/setting-translation-checks#section-custom-variables). Since this tool gives tons of flexibility it is fairly easy to go overboard, so here are some tips about setting proper placeholders to protect exactly what you need. Any placeholder set you add in the respecting field is checked via regular expression matches, so the more specific you are the better! A typical exam… --- _[View the full topic](https://community.transifex.com/t/custom-placeholders-for-untranslatable-variables/54)._