You embedded an absolute URL to an image file in your page HTML? You know, if you ever move this site to a server instead of running it on your local PC, you'll have to update the URL? Instead, you should be using relative or root relative paths. Here's a link explaining the difference.
–
masonMay 8 '14 at 13:31

I am giving localhost absolute path. I also tried by giving online image path but it is not rendering images. But if i give inline html to C# page and pass image url from there it render this properly
–
Muhammad zubairMay 8 '14 at 13:42

I think the issue you're going to face is that iTextSharp does not handle conversion of HTML to PDF seamlessly, probably because it's a bad idea to attempt anyways. Web pages are designed to be accessed from web browser. Instead, you should be building up your PDF programmatically which gives you fine grained control over the document.
–
masonMay 8 '14 at 13:53

@mason, absolute image paths make path resolution much easier for iTextSharp so for this specific case that is a proper solution. Also, I wouldn't go so far as to say that HTML to PDF is a bad idea. Adobe has been doing it for many years and iText has two HTML to PDF translators. If you're not willing to put in the time to learn the PDF language and/or iText's abstractions and are also willing to accept some sacrifices in control then the HTML to PDF is probably the best option.
–
Chris HaasMay 8 '14 at 14:17