Is the state of the obfuscated image still related somehow to the state of the non-obfuscated version? If yes, your obfuscation method sucks.
You need to change the image in such a way that the state of the obfuscated part after you apply the method is not related in any way to its state before. Otherwise clever algorithms will always find a way to "leak" info out of your poor choice of method.
The best thing is to just drop a black (#000000) blob over the relevant part, completely replacing the part snd deleting previous bits 100%. There's no information leak other than size then.
Blurring algos, pixelation, all that fancy stuff from the movies looks good on screen but is naive in practice.
Of course, if you use a "smart" file format that has undo history and such, then you might still be leaking info.
(you can of course cover something up with a random pixelated pattern if that looks less jarring, but it then is a purely cosmetic choice: the important bit is to remove all information connected to the obscured content)
Actually, quite a few times in the past with that method, you've gotten the complete text, because someone uses a format that includes the text as text (like PDF) and then dropped a solid-black box over the text, which looks like the text is obliterated, but preserves the entire content in the file.
Unfortunately, they did this without disabling the Excel feature that saved undo data in the file, so anyone in the class was able to hit Ctrl+Z a couple of times and see the entire list of grades.
Of course, if you block out a whole line, then things get much, much harder, basically impossible. There are many possible lines!