TL;DR: CPython stores strings using PEP 393 (Flexible String Representation) rather than UTF-8. It selects a fixed width of 1, 2, or 4 bytes per character based on the widest character present. If an ASCII string contains just one 4-byte emoji, Python instantly upgrades every single character in that string to 4 bytes, quadrupling its memory footprint.

Imagine loading a massive log file into memory, doing basic parsing, and watching your server's RAM jump from 100 MB to 400 MB. You haven't added millions of extra records—you just processed a line containing a single thumbs-up emoji. When I profile Python memory footprints, I often see engineers get tripped up by this exact behavior. This isn't a memory leak; it's a deliberate architecture trade-off built into CPython.

How Does Python Store Strings in Memory?

CPython stores strings using PEP 393, known as the Flexible String Representation, rather than variable-width UTF-8 encoding.…