# YAML syntax error -- control characters are not allowed at line 1 column 1

**URL:** <https://meta.discourse.org/t/yaml-syntax-error-control-characters-are-not-allowed-at-line-1-column-1/119422>\
**Category:** Product Support\
**Created:** [June 3, 2019, 9:51pm UTC](https://meta.discourse.org/t/yaml-syntax-error-control-characters-are-not-allowed-at-line-1-column-1/119422 "2019-06-03T21:51:54Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![jks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jks/32/101841_2.png) [@jks](https://meta.discourse.org/u/jks)\
**Post date:** [June 4, 2019, 1:16pm UTC](https://meta.discourse.org/t/yaml-syntax-error-control-characters-are-not-allowed-at-line-1-column-1/119422/12 "2019-06-04T13:16:39Z")

</div>

I see you solved this already, but in my experience weird control characters at the beginning of a file usually result from editing in some GUI editor that likes to add the [byte-order mark](https://en.wikipedia.org/wiki/Byte_order_mark) to text files. They could be invisible, but when you run some tool like `hexdump -C` on them, you see the extra bytes:

```plaintext
00000000 ef bb bf 73 6f 6d 65 20 74 65 78 74 20 68 65 72 |...some text her|
00000010 65 0a |e.|
00000012

```

---

_[View the full topic](https://meta.discourse.org/t/yaml-syntax-error-control-characters-are-not-allowed-at-line-1-column-1/119422)._
