Sometimes, yes. Blur and pixelation are transformations of the original pixels, not deletions, and a transformation can be undone when the attacker knows enough about the input. That is why every serious redaction guideline, from courts to security teams, says the same thing: cover, don't smudge.
Pixelation replaces each block of pixels with their average. For text in a known font and size, an attacker can render candidate characters, pixelate them the same way, and compare against your image block by block. Short, high-value strings such as passwords, account numbers and license plates are the easiest targets because the search space is small. Open-source tools have demonstrated this against pixelated text since 2020, and the technique gets stronger every year as the models improve.
Gaussian blur spreads each pixel's value over its neighbors. Mathematically it's a convolution, and convolutions can be partly inverted (deconvolution) when the blur radius is guessable, which it usually is, because most tools use a handful of presets. Real-world recovery is less reliable than with pixelation, and heavy blur on long text is often unrecoverable in practice. But "often" is a bad word to build a privacy process on, and a blurred number is also a signal that there is a number there worth attacking.
Because it looks nicer, and because for low-stakes content (a stranger's face in a crowd, a random background window) it's fine. Cloakshot's editor offers blur and pixelate for exactly that, and uses solid black by default for everything it detects, because the things it detects are precisely the things worth attacking.
One click blacks out emails, phone numbers, card numbers, IDs, API keys and IPs before the screenshot is taken. Free for 5 auto-redacted captures a day. Nothing leaves your browser.
Get Cloakshot for Chrome