diff --git a/README.md b/README.md
index 5281c2d..44eb4d3 100644
--- a/README.md
+++ b/README.md
@@ -51,7 +51,7 @@ To test the security products in your reach you should generate two pairs of sam
 
 After the samples are ready follow the methodology shown on the diagram below:
 
-![Testing Methodology](testing_methodology.svg "Testing Methodology")
+![Testing Methodology](testing_methodology.png "Testing Methodology")
 
 (*) If the product is not able to detect the first malicious sample, there are more serious problems to worry about than crypto-fu. In fact, the simple cryptography included in the provided boilerplate code poses as a hard challenge for various products... Try to use more obvious samples!
 (**) The product most probably uses some trivial method to detect the boilerplate insted of the actual payload. You can try to introduce simple changes to the code like removing debug strings.