ByteScout PDF Extractor SDK – ASP.NET C# – Extract Images from PDF

  • Home
  • /
  • Articles
  • /
  • ByteScout PDF Extractor SDK – ASP.NET C# – Extract Images from PDF

ByteScout PDF Extractor SDK – ASP.NET C# – Extract Images from PDF


using System;
using System.Collections.Generic;
using System.Drawing.Imaging;
using System.IO;
using Bytescout.PDFExtractor;

namespace ExtractImages
	public partial class _Default : System.Web.UI.Page
		protected void Page_Load(object sender, EventArgs e)
			String inputFile = Server.MapPath(@".\bin\sample1.pdf");

			// Create Bytescout.PDFExtractor.ImageExtractor instance
			ImageExtractor extractor = new ImageExtractor();
			extractor.RegistrationName = "demo";
			extractor.RegistrationKey = "demo";
			// Load sample PDF document

			// Array to keep extracted images
			List<byte&#91;&#93;> extractedImages = new List<byte&#91;&#93;>();

			// Initialize image enumeration
			if (extractor.GetFirstImage())
					// Extract image to memory
					using (MemoryStream memoryStream = new MemoryStream())
						extractor.SaveCurrentImageToStream(memoryStream, ImageFormat.Png);
						// Keep image as byte array
				while (extractor.GetNextImage()); // Advance image enumeration
			// Write first image to the output stream


			Response.ContentType = "image/png";
			Response.AddHeader("Content-Disposition", "inline;filename=image.png");



<?xml version="1.0"?>

            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.
        <compilation debug="true" />
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
        <authentication mode="Windows" />
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />

  Click here to get your Free Trial version of the SDK