Yeah, I considered that, but I figured it would've been pretty dumb in practice. It would have been better to make similar code in another language to actually fix the images instead if I were to do that. Though, it would read from the bitmap control and not the image, correct? So, the issue would still remain where you need to have an idea of where the image starts and stops, since it would read the wrapped or scaled image rather than the original image.