Just output the data to a text log via error_log($data,3,_DIR_.'/debug. To look at the source code, not on the render page (Ctrl+U like) Tell them that you send the data in utf-8 encoding using header('Content-Type: text/html charset=utf-8') Tell them that you are sending text data rather than html, using header('Content-Type: text/plain charset=utf-8') More specifically, your mistake is that you didn't use any of the options to see the data 'as is' and not told the browser what kind of data you pass him. Yes, it's convenient, but in doing so you unknowingly rely on heuristics of the browser - this is what leads to the effect you described. You're trying to force the browser to interpret your, in fact, the output in the debug log do not worry about how to explain to the browser what you sent to him. Of course kasetsat browser shows what he sent, at the level of ordinary life experience this is the case, but as a developer you have to remember that the browser is a very complex system and its task is to render the submitted html pages. This is because you are viewing the server response in the browser instead of viewing it in the original. Click 'Format' from the toolbar at the top of the window. Идем дальше, при декодировании json меняется кодировка на ASCII, почему? Regarding this, how do I change the font in my Thunderbird signature Press 'Ctrl' and 'A' to highlight all the signature text you just typed. When output to screen via php coding breaks down, but if you check the encoding of this string using mb_detect_encoding(), the UTF-8 encoding. When you view the cookies through the debugger (F12) the encoding is correct. Cookies lies in the json string with UTF-8 encoding.

Change text encoding chrome