When I try to cite more than two authors, I got this:

! Package inputenc Error: Unicode char ​ (U+200B)
(inputenc)                not set up for use with LaTeX.




  • 1
    unrelated to the error you are missing a { before key3} Commented Feb 7, 2017 at 23:49
  • The problem usually comes from copying and pasting between text files that use different encodings. Notepad++ makes toggling encoding simple. I simply copy the entire text into it and convert to whatever coding I am using and this problem usually goes away.
    – Dan Fox
    Commented Dec 28, 2021 at 17:57

2 Answers 2


U+200B is zero width space which you have here:


from the end of this line


is (using this unicode converter)

  U+200b ZERO WIDTH SPACE     ​ 
  U+007d RIGHT CURLY BRACKET     } } \rbrace

delete that line and re-type without the invisible control characters between the m and }

  • 1
    Nice! Thank you so much! Now it works perfectly!
    – user124801
    Commented Feb 7, 2017 at 23:53
  • So this worked perfectly. Thank you. I deleted a whole line and retyped it and it worked. How did David generate the output in the bottom box with the character codes? I tried blindly finding the ZWS blindly but didn't manage until I deleted the whole line.
    – Cyrille
    Commented Dec 19, 2017 at 22:18
  • 4
    @Cyrille I cut the text where I suspected the character into w3c.github.io/xml-entities/unicode-names.html and hit "convert" (a javacscript page that I wrote some time ago) Commented Dec 19, 2017 at 22:32
  • Thanks @DavidCarlisle that will be a helpful resource in the future. I have gone ahead and added the link in your answer.
    – Cyrille
    Commented Dec 21, 2017 at 9:40
  • I just had same problem and fix was same. I don't understand how the invisible character gets into a raw text document that I'm editing with Emacs. Caused by cut-and-paste from some other format? I found out later I could view the TeX file in Texworks and it did show the U+200b literally on screen, so I could see it was there. It did not show in Emacs, but I could move cursor left and right and you can tell there is something invisible because column number changes as cursor seems to stay on same spot.
    – pauljohn32
    Commented May 26, 2018 at 18:26

This is one of the top hits for U+200B and LaTeX, so I’ll post solutions here.

Take the following example:

\begin{document}f​l f‌l fl\end{document}

In LuaLaTeX, it compiles to:

Latin Modern font sample

The first fl has no ligature because I inserted U+200B, a zero-width space. The second has no ligature because I inserted U+200C, a zero-width non-joiner. These might have been in the original source you copied from intentionally: a zero-width space could mean a potential line break, such as after a slash, and a zero-width non-joiner disables a ligature. For example, the fi in Elf‌in or the fl in Half‌ling are (according to pedants like me) not supposed to be ligated, since they belong to different pieces of a compound word. Almost no one bothers to actually do that, but it is much more common in some other languages.

If you try to compile it in PDFLaTeX, you will get the error message that brought you here:

! Package inputenc Error: Unicode character ​ (U+200B)
(inputenc)                not set up for use with LaTeX.

There are several ways to fix it.

Clean Your Source by Hand

This is what most people on this site recommend. Your editor might have a way to display special characters so you can delete them all. But really, isn’t this a job for a computer?

Clean your Source in your Editor

This is harder with an invisible, zero-width character, but you might be able to copy zero-width space from a character map, open up your search-and-replace dialogue box and paste the character into the search field. You can then replace it with something like ZWS or {\hskip 0pt}.

Clean Your Source with Perl

The following one-line Perl script will create a new source file with all zero-width spaces removed:

perl -CSD -pe "s/\N{U+200B}//gu" < U200B.tex > noU200B.tex

If it’s easier to remember, you could also write this as

perl -CSD -pe "s/\N{ZERO WIDTH SPACE}//gu" < U200B.tex > noU200B.tex

The -CSD option selects UTF-8 unconditionally, even if you don’t have UTF-8 as your default locale. The -pe option runs the given Perl script on the input file and prints to the output file. The s command does substitution, the \N{...} is a regular expression matching zero-width space, the empty field between // means replace with nothing, and gu means replace all instances globally in the unicode string. Then, the < and > operators select the input and output files.

Either of these produce a file that compiles to:

Computer Modern Font sample

It’s also possible to automatically remove all characters outside a given subset. The script

perl -CSD -pe "s/[^\p{Word}\p{Punct}\p{Symbol}\p{Mark}\p{PerlSpace}]//gu"

allows only the following: Unicode “word” characters, punctuation, symbols, accents and a few kinds of spaces. It erases most invisible characters. An even more restrictive version would be

perl -CSD -pe "s/[^\p{ASCII}]//gu"

This cleans out all characters but for the ASCII originally allowed in TeX (including instead of double backtick).

And yes, we could replace zero-width space by something instead of nothing. The script

perl -CSD -pe "s/\N{ZERO WIDTH SPACE}/{\\\\hskip 0pt}/gu; s/\N{ZERO WIDTH NON-JOINER}/{}/gu"

given the above MWE as input, produces the following output:

\begin{document}f{\hskip 0pt}l f{}l fl\end{document}

Teach LaTeX to Understand Zero-Width Space

If the problem is that U+200B is “not set up for use with LaTeX,” but it’s equivalent to a TeX command—\hskip 0pt or \hspace{0pt} are zero-width spaces that prevent ligatures and enable a potential line break—we can set the character up to use that command.


  \usepackage[utf8]{inputenc} % The default since 2018
  \DeclareUnicodeCharacter{200B}{{\hskip 0pt}}

\begin{document}f​l f‌l fl\end{document}

Although the \DeclareUnicodeCharacter command is in inputenc, the LaTeX kernel has loaded it by default since 2018. So, we could have skipped declaring it.

  • Copying the zero-width-space character and replacing it helped. This is mad though.
    – Anna
    Commented Apr 3 at 13:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .