Technical FAQs

Question

If I have a PDF document that only has an embedded image in it (no text objects, etc.), can PrizmDoc Viewer take it and create a searchable PDF file from it?

Answer

Yes. PrizmDoc’s Content Conversion Services can take an image-only PDF and create a searchable PDF file from it. This can be done by modifying the input.dest.pdfOptions.ocr options object; see our documentation here.

If you are attempting to make a searchable PDF from an existing PDF document, please note that the source PDF file should be an image-only PDF. PrizmDoc will not create a searchable file from already-existing vector content.

This feature was introduced in PrizmDoc 13.1, please see our Release Notes for more information.

Question

If I have a PDF document that only has an embedded image in it (no text objects, etc.), can PrizmDoc Viewer take it and create a searchable PDF file from it?

Answer

Yes. PrizmDoc’s Content Conversion Services can take an image-only PDF and create a searchable PDF file from it. This can be done by modifying the input.dest.pdfOptions.ocr options object; see our documentation here.

If you are attempting to make a searchable PDF from an existing PDF document, please note that the source PDF file should be an image-only PDF. PrizmDoc will not create a searchable file from already-existing vector content.

This feature was introduced in PrizmDoc 13.1, please see our Release Notes for more information.

Although often considered a bit old fashioned, the insurance industry has made great strides in recent years to adapt to the changing needs of its customers. The latest generation of insurance customers expects faster service, better support, and more options from providers. Given these pressures, it’s no surprise that InsurTech developers have found ample opportunities to deliver solutions that help insurance firms better manage their workflows and create better customer experiences.

Despite the successes of this digital transformation, however, there are still a number of challenges that InsurTech developers face when building new applications. Investing heavily in creating powerful AI and big data tools might help those platforms stand out from the crowd, but they won’t find much success with firms if they don’t also provide the core functionality organizations need to service their customers. 

That’s why many InsurTech developers are turning to versatile SDK and API integrations to expand their feature sets without compromising their development timelines.

4 Major Challenges of InsurTech Applications

1. Security and Privacy

As the insurance industry continues to shift toward digital processes and platforms, it’s become more important than ever for InsurTech applications to keep sensitive data secure. While most organizations do invest in cybersecurity protections, they often don’t realize how their own practices could potentially pose a risk to customer information. This is especially true of insurers that rely on third-party programs for various tasks like document viewing and editing. Take, for instance, the case of Folksam Group, which inadvertently shared client data from as many as one million customers with Google, Facebook, LinkedIn, Microsoft, and Adobe in late 2020. 

2. File Management

Today’s insurers are receiving all kinds of documents, files, and images from their customers, which creates something of a document dilemma. A single auto accident claim, for instance, might have valuable information spread across multiple PDFs, Word documents, spreadsheet files, scanned images of hand-written forms, and image files. In order to process claims quickly and effectively, firms need InsurTech solutions that provide an all-in-one solution that can handle a broad array of file formats. Without these file management tools, insurers will be forced to use multiple programs to meet their needs, which creates inefficient dependencies and increases security risks.

3. Data Collection

Insurance companies gather quite a bit of information from form applications, both in physical and digital formats. Unfortunately, transferring that information from a form document into an InsurTech system is often a laborious manual process. Not only is manual data collection time consuming, it also increases the likelihood of human error. Even when firms do implement an InsurTech solution with forms processing capabilities, however, they often lack the capability to read certain types of form fields, especially those completed by hand. The ability to adapt to new form templates is also critical for organizations that want to invest in automation. 

4. Remote Collaboration

The COVID-19 pandemic may have forced insurance offices to rapidly embrace a remote work strategy, but many firms had already been investing in some form of hybrid work model for years. Nationwide was able to transition 98 percent of its workforce to remote status precisely because the company already had the technology solutions in place to allow insurance agents to work from home. Without some way of facilitating remote collaboration directly through InsurTech applications, organizations end up relying on email, which poses serious security concerns. Furthermore, with multiple copies of a document being distributed and downloaded, it quickly becomes difficult to know which version incorporates the most up-to-date changes.

SDK and API InsurTech Solutions

Building new functionality into an application always involves a tradeoff. When developers choose to code something from scratch, that means pulling team members away from another project or extending the product’s release timeline. In a fast-moving industry where InsurTech developers are racing competitors to be the first to market, it doesn’t make sense to design and build every aspect of an application in-house. 

Rather than pulling valuable development resources away from their innovative InsurTech features, developers can solve common insurance challenges much faster with SDK toolkits and API integrations. 

Secure File Viewing

The easiest way for InsurTech solutions to keep documents secure is to integrate HTML5 viewing capabilities directly into the application. Rather than being forced to download or open a file for viewing in a third-party application, employees can view multiple document formats natively. This is critical because it means no data will be shared with third-party programs.  Since the files remain safely within the secure InsurTech environment, firms can also control the level of access to any document, which prevents unauthorized individuals from downloading or viewing the contents. Thanks to API-based integrations like Accusoft’s PrizmDoc Viewer, InsurTech developers can help their applications safely view more than 100 unique file types without any third-party dependencies.

Data Capture

By integrating forms processing capabilities into their applications, InsurTech developers can provide their clients with powerful tools that allow them to gather essential data quickly and accurately. As the essential connective tissue between customers and insurance databases, form field recognition integrations use OCR technology to intelligently identify form data and extract it for processing. They can also be set up to identify a wide range of insurance forms to quickly identify and scan documents to streamline processing workflows. Accusoft’s FormSuite for Structured Forms even goes a step further by incorporating powerful image cleanup functionality to ensure that data will be extracted as accurately as possible.

File Conversion

In order to meet the file management challenges of today’s insurance providers, InsurTech developers need document and image processing integrations that can read and write multiple file formats. Information spread across multiple documents, emails, or even texts can be processed using OCR technology, and then consolidated and converted into a variety of formats for easy reference and collaboration. Rather than juggling several files with different dependencies, an SDK integration like Accusoft’s ImageGear can easily output processed files in PDF, RTF, XML, or DOCX format for viewing and editing within a single application.

Editing and Annotation

Providing secure document viewing capabilities solves only one half of the insurance collaboration challenge. InsurTech applications also need to provide both internal and external stakeholders with the ability to edit and markup documents throughout the application and claims process. Content processing integrations can allow authorized users to make changes to documents completely within their InsurTech solution and review markups and comments from other collaborators. 

Since all editing occurs within the application itself, there’s no need to worry about anyone downloading a document to make changes locally and creating confusion over which version is the most up-to-date. Redactions may also be necessary to hide private or confidential information from unauthorized viewers. As an added benefit, PrizmDoc Viewer’s editing features allow users to make a variety of markups and redactions while preserving the integrity of the original file.

Accelerate Your InsurTech Application Development with Accusoft

Accusoft’s collection of powerful SDK toolkits and API integrations provide innovative InsurTech developers with the resources they need to solve core insurance industry challenges. By implementing proven functionality into their applications, project managers can streamline the development process and dedicate more resources to the innovative features that will set their platform apart from the competition.

Whether you’re looking to incorporate versatile document viewing and editing or need a more accurate forms processing solution, Accusoft’s family of InsurTech SDKs and APIs can help your development team get to market faster. Learn more about what our products can do for your application in our InsurTech fact sheet.

 

Question

Sometimes, when redacting an Office or PDF document, redactions drawn over certain content (such as an image or a logo) appears to get burned on other occurrences of the image on other pages. Why does this happen?

Answer

The reason why the duplicate redactions are occurring is because the images are shared images. In PrizmDoc, when a change is made to one instance of the shared image, it gets applied to every other instance. Per engineering, this is to mimic the behavior of Adobe Acrobat.

There currently exists a feature request to allow shared images to be treated as individual images so that they could be redacted separately:

https://ideas.accusoft.com/ideas/PDV-I-655

Barcode Xpress ImageGear .NET

Barcode Xpress and ImageGear .NET.  Barcode Xpress is a leading barcode reading SDK. While it supports a variety of image formats, Barcode Xpress works with ImageGear to support even more obscure image formats. For example, Barcode Xpress does not support reading barcodes on PDFs. Combined with ImageGear, developers can support a myriad of image formats and PDFs. With Barcode Xpress & ImageGear working together, developers can integrate a barcode reader that can detect barcodes on almost any kind of document.

Barcode Xpress accepts images in multiple different object types, such as System.Drawing.Bitmap. Using the method ImGearFileFormats.ExportPageToBitmap we can easily take any image that ImageGear supports and export it to a System.Drawing.Bitmap object that we can then pass to Barcode Xpress. So, only a tiny amount of code is required to recognize barcodes with ImageGear .NET and Barcode Xpress. Below, we’ll show various ways to pass different types of images and documents to Barcode Xpress.


Image:

// Load the image into the page.
ImGearPage imGearPage = ImGearFileFormats.LoadPage(stream, 0);

// Export the image to a bitmap and pass that bitmap to Barcode Xpress
 Result[] results = barcodeXpress.reader.Analyze(ImGearFileFormats.ExportPageToBitmap(imGearPage));


PDF:

We need slightly more code for a PDF. First, we specify a page number when calling LoadPage. Second, we must dispose of the ImGearPage object after we’re done with it. 

// Load the specified page of the PDF as an ImGearPage object
ImGearPage imGearPDFPage = ImGearFileFormats.LoadPage(stream, pageNumber);

// Export the image to a bitmap and pass that bitmap to Barcode Xpress
Result[] results = barcodeXpress.reader.Analyze(ImGearFileFormats.ExportPageToBitmap(imGearPDFPage));

(imGearPDFPage as IDisposable).Dispose();

Now that we’ve explained the most important part, we’ll show you a simple console app that recognizes barcodes on a PDF using the method above. 

The code below assumes you’ve installed an evaluation or development license for both Barcode Xpress and ImageGear .NET.

using System;
using System.IO;
using Accusoft.BarcodeXpressSdk;
using ImageGear.Core;
using ImageGear.Evaluation;
using ImageGear.Formats;
using ImageGear.Formats.PDF;

namespace BXandIGDotNet
{
	class Program
	{
    	static int pageNumber = 0;
    	static string fileName = @"Path/To/Your/PDF..pdf";
    	static void Main(string[] args)
    	{
        	// Initialize evaluation license.
        	ImGearEvaluationManager.Initialize();

        	// Initialize common formats.
        	ImGearCommonFormats.Initialize();
        	// Add support for PDF and PS files.
        	ImGearFileFormats.Filters.Insert(0, ImGearPDF.CreatePDFFormat());
        	ImGearFileFormats.Filters.Insert(0, ImGearPDF.CreatePSFormat());
        	ImGearPDF.Initialize();

        	using (FileStream stream = new FileStream(fileName, FileMode.Open, FileAccess.Read, FileShare.Read))
        	using (BarcodeXpress barcodeXpress = new BarcodeXpress())
        	{
            	// Load the specified page of the PDF as an ImGearPage object
            	ImGearPage imGearPDFPage = ImGearFileFormats.LoadPage(stream, pageNumber);

            	// Export the image to a bitmap and pass that bitmap to Barcode Xpress
            	Result[] results = barcodeXpress.reader.Analyze(ImGearFileFormats.ExportPageToBitmap(imGearPDFPage));

            	(imGearPDFPage as IDisposable).Dispose();

            	// Print the values of every barcode detected.
            	for (int i = 0; i < results.Length; i++)
            	{
                	Console.WriteLine("#" + i.ToString() + " Value: " + results[i].BarcodeValue);
            	}
            	Console.ReadKey();
        	}
    	}
	}
}

Using Barcode Xpress and ImageGear in Other Languages & Linux

You can also use Barcode Xpress and ImageGear together outside of the .NET framework. Barcode Xpress supports several different programming languages and frameworks including .NET Core, Java, NodeJS, Python, C, and C++. All of which can be used on Linux. 

ImageGear for C/C++ also supports Linux. Barcode Xpress Linux, which is a C/C++ library, ships with a sample called “ReadBarcodesIG”, that shows how to integrate Barcode Xpress Linux and ImageGear for C/C++. You can find the sample code after downloading our SDK here! For more information on Barcode Xpress, visit our Developer Resources page on the website. In addition, you can also find more information about ImageGear .NET on its respective Developer Resources page as well.

Question

What are the differences between the compressions used in TIFF files?

Answer

The Tagged Image File Format (TIFF) is widely popular, and is particularly used in document imaging. It can support a number of compression types:

  • Packbits – Created by Apple, this lossless compression type is used for run-length encoding (RLE). Baseline TIFF readers must support this compression. Use this compression for higher compatibility with various applications.
  • CCITT (Huffman encoding) – Used particularly for encoding bitonal (or bi-level) images. “Group 3” and “Group 4” are particularly known for its use with fax transmission of images. Using this compression type will help keep smaller file sizes.
  • LZW – A lossless compression type that supports multiple bit depths. Because it’s lossless, it produces files that are generally larger than other compressions. Use this compression if you want to retain the exact visual quality of the image without data loss or artifacts.
  • JPEG – Very popular compression, used for color and grayscale images and can produce high compression ratios. JPEG allows a good amount of control over how the image in question should be compressed. Use this compression for general color or grayscale images.
  • Deflate – A lossless compression using Huffman and LZ77 techniques and also supports different bit depths.

.net document viewer

Adding document viewing features to an application can be a challenge. Although there are many open source options available, finding a suitable ASP.NET document viewer or .NET image viewer that provides the right level of flexibility and functionality often requires a more specialized solution. Fortunately, .NET developers have good options when the time comes to integrate document viewing into their software, which helps them to focus on other application features.

The API Document Solution

Rather than building a dedicated viewer within their .NET application, many developers instead turn to an HTML5 viewer integration that uses REST APIs for their document needs. Since these viewers work within the web browser and can support any programming language, they provide the right balance of versatility and performance for most software applications. An HTML5 document viewer ensures a consistent viewing experience across multiple software platforms and browsers used within an enterprise environment.

Of course, if all an application needed to do was view files, it could simply use one of many open-source solutions. The problem is that these viewers typically only view one type of file, which means that the application also needs the ability to convert files into different formats. Depending upon the library in question, this could quickly escalate into a code-heavy solution that bogs down application performance and introduces multiple security vulnerabilities. If poor conversion tools are put in place, there’s also a strong likelihood that documents will not render accurately.

An HTML5 viewer with the right APIs can easily overcome these document management challenges for a .NET application. Conversion, annotation, comparison, and redaction features can all be integrated as part of a comprehensive viewing framework that doesn’t require developers to build anything from scratch or rely upon intrusive plugins that create risky dependencies.

How Accusoft APIs Enhance Your .NET Application

Accusoft’s PrizmDoc Viewer was designed to provide a broad range of document processing capabilities in addition to its core HTML5 viewing features. Once integrated into a .NET application, it allows developers to deploy REST API calls to convert files into new formats, split and merge documents, create page thumbnails, markup documents, and perform high-volume text searches. As an HTML5 viewer, PrizmDoc Viewer can deliver all of that functionality right within the browser rather than resorting to external applications.

The primary advantage of REST APIs is that they can be used from any programming language, so they don’t have to be custom-built to serve as an ASP.NET document viewer. That versatility does come with a tradeoff, however. Processes like uploading files, converting them, and then downloading outputs all require a series of HTTP requests. While this isn’t a particularly difficult process, it is slightly more resource-intensive than a solution built using the same programming language as the application. 

That’s why we developed a .NET SDK library that wraps around the server-related functions of PrizmDoc Viewer. Available for both .NET Core and .NET Framework, this SDK library wraps around the server’s REST APIs to make it easier to utilize server functionality in .NET applications.

For .NET developers looking for a better way to view and process documents, the PrizmDoc .NET SDK can help them access conversion, redaction, and annotation features without compromising the performance of their .NET applications.

Getting Started with PrizmDoc .NET SDK

In order to implement the .NET wrapper, developers just need to follow a few simple steps. 

1. Gain Access to a PrizmDoc Server Deployment

There are two ways to access PrizmDoc Server, which will allow you to carry out a variety of document processing functions. You can host a server on-premises as part of a PrizmDoc Viewer integration or sign up for a PrizmDoc Cloud account to use Accusoft’s cloud-hosted deployment.

2. Add the PrizmDoc Server .NET SDK Package

Next, download the free, open source .NET SDK library from NuGet or GitHub and add it to your application project.

dotnet add package Accusoft.PrizmDocServerSDK

 

3. Create a new PrizmDocServerClient

Once the .NET wrapper is in place, it’s time to construct a new PrizmDocServerClient and connect it to the server.

For a self-hosted PrizmDoc Server that’s part of a PrizmDoc Viewer deployment, the base URL is all that’s needed:

var prizmDocServer = new PrizmDocServerClient("http://localhost:18681");

 

If the you’re using PrizmDoc Cloud, you’ll need to provide the base URL along with your API key:  

var prizmDocServer = new PrizmDocServerClient("https://api.accusoft.com", "YOUR_API_KEY");

 

4. Begin Document Processing

Now that everything is in place, you can start processing and viewing documents within your .NET application. Our How To Guides provide some examples of common use cases, and you can also turn to the API Reference for additional guidance and information.

Get the Document Viewing Features Your .NET Application Needs

Accusoft’s PrizmDoc Viewer delivers the versatile HTML5 viewing capabilities that can set your .NET application apart from the competition. Thanks to the PrizmDoc Server .NET SDK wrapper, you can leverage the power of our REST APIs without needing to build out a customized viewing solution from the ground up.

Find out how easily you can manage your document needs with PrizmDoc Viewer’s browser-based functionality today. Sign up for a free trial to test our HTML5-powered viewer in your .NET environment.

Question

When printing in PrizmDoc, the bottom of my document is being cut off. Why is this happening?

When I download the document as PDF, I do not lose parts of the document. However, if I print the document to PDF, I lose some data off the very bottom (maybe an inch or so).

Answer

In PrizmDoc, the page is to "fit to width" onto the paper by design. The bottom of the page will be cut off in cases where the length of the page extends further than the length of the paper. If you’re printing with Letter size paper (the default), it presumes a document that measures 8.50 by 11.00 inches. Suppose your document measures 8.50 x 13.00 inches. That additional 2 inches will be cut off during printing. This is why you may lose parts of the document while printing, but not if you download the document since it’s downloading the document as-is.  

To prevent this from happening, select a paper size large enough for your document (in the viewer print dialog and the system print dialog). Using the previous 8.50 x 13.00 inch example, you can select "Legal" size paper, which measures 8.50 x 14.00 inches, and would be long enough to support that document.

You could also modify your viewer to add a custom paper size if this fits your use case. Below is some sample code demonstrating this in our Viewer sample. You would need to enter your own custom paper sizes.

https://www.accusoft.com/code-examples/printing-custom-paper-sizes/

Changes to printTemplate.html:

    /*custom */
    .portrait .custom.page { width: 11in; height: 11in; margin: 0 auto !important; }
    .portrait .custom.pageIE { width: 9.5in; height: 9.5in; margin: 0 auto !important; }
    .portrait .custom.pageSafari { width: 8.9in; height: 8.9in; margin: 0 auto !important; }
    .portrait .custom.nomargins { width: 11in !important; height: 11in !important; }
    /* even without margins, Safari enforces the printer's non-printable area */
    .portrait .custom.nomargins.pageSafari { width: 9.32in !important; height: 9.32in !important; }
    
    .landscape .custom.page { height: 11in; width: 11in; margin: 0 auto !important; }
    .landscape .custom.pageIE { height: 9.05in; width: 9.05in; margin: 0 auto !important; }
    .landscape .custom.pageSafari { height: 8.4in; width: 8.4in; margin: 0 auto !important; }
    .landscape .custom.nomargins { height: 11in !important; width: 11in !important; }
    .landscape .custom.nomargins.pageSafari { height: 9.32in !important; width: 9.32in !important; }
    /*custom end*/

Changes to printOverlayTemplate.html (last line "Custom" is the only change):

    <select data-pcc-select="paperSize" class="pcc-print-select">
        <!-- US and International-->
        <option value="letter"><%= paperSizes.letter %></option>
        <option value="legal"><%= paperSizes.legal %></option>
        <option value="tabloid"><%= paperSizes.tabloid %></option>
        <option value="foolscap"><%= paperSizes.foolscap %></option>
        <!-- A formats-->
        <option value="a3"><%= paperSizes.a3 %></option>
        <option value="a4"><%= paperSizes.a4 %></option>
        <option value="a5"><%= paperSizes.a5 %></option>
        <!-- Architectural-->
        <option value="a6"><%= paperSizes.a6 %></option>
        <option value="a"><%= paperSizes.a %></option>
        <option value="b"><%= paperSizes.b %></option>
        <option value="c"><%= paperSizes.c %></option>
        <option value="d"><%= paperSizes.d %></option>
        <option value="e"><%= paperSizes.e %></option>
        <option value="e1"><%= paperSizes.e1 %></option>
            
        <option value="custom">Custom</option>
    </select>

Additionally, if you would like to change the default selected page size you can add selected to it as follows:

<option value=\"a4\" selected><%= paperSizes.a4 %></option>

The COVID-19 pandemic may not be the first pandemic to impact global supply chains, but its impact has been orders of magnitude greater than previous public health crises. Businesses around the world have been forced to contend with the twin challenges of transitioning to a remote workforce and overcoming severe supply chain disruption. As 2020 winds down to a close, it’s becoming clear that the pandemic may well represent a “new normal” for logistics strategy rather than a temporary situation.

3 Critical Supply Chain Challenges 

From implementing new technology to establishing relationships with alternative vendors, organizations across multiple industries are taking steps to meet the challenges confronting their supply chains in both the immediate and long-term future. One of the biggest areas of focus is barcode integration. Although they may not seem like they belong at the forefront of innovation, barcodes are scanned more than six billion times every day and serve an incredibly important role in modern supply chain management.

Here are a few of the biggest challenges organizations are facing:

1. Supply Chain Visibility

Speed and flexibility are competitive advantages in today’s on-demand marketplace. Customers want products delivered faster and will quickly lose faith in brands that fail to meet their expectations. According to a 2019 survey of online consumers, 72.7% of respondents were unlikely to order from a company again after a poor delivery experience. Given those high stakes, it’s incredibly important for organizations to maintain high levels of visibility into their supply chains.

Barcode technology makes it possible to track products and materials throughout the entire production and distribution process. A quick scan is all that’s needed to update an item’s status every time it’s processed at a location. That information feeds into inventory tracking software that allows businesses to get a more accurate picture of how shipments move through their supply chain. This visibility makes it easier to identify potential problems and enhance overall logistics efficiency. 

2. Digital Transformation

Despite the growing emphasis on digital transformation across the economy, the average supply chain is still held back with inefficient, legacy infrastructure. Small and medium-size businesses face the greatest challenges, with only 21% of them using digital tools to integrate their supply chain operations with other departments. In the retail industry alone, bad processes and data disconnects cost companies over $500 billion annually. As the holiday season draws nearer and promises to bring with it a massive increase in online shopping, having a fully digital supply chain in place with enough speed to handle that demand is essential.

Implementing the right digital technology tools can help organizations to streamline their supply chains and gather the data they need to make better decisions. Barcode integration software is a foundational component of this transformation because it forms a bridge between the physical and digital elements of logistics management. Shipments can be instantly scanned into tracking systems to provide a wealth of data points across the supply chain, making it easier to adapt to disruptions and develop better processes. Barcode libraries also need to be able to scan and decode both traditional 1D codes and newer 2D codes quickly and accurately to keep products moving swiftly and smoothly to consumers.

3. Automation

As many organizations have put social distancing protocols in place during the pandemic to protect the health of both employees and customers, automation has become more important to supply chain performance than ever before. These COVID-19 pressures are sure to accelerate what was already a growing push toward implementing automated software and systems. Gartner even projected in 2019 that 30% of warehouse workers will be replaced by collaborative robots by 2023, which will further drive the demand for automated scanning and inventory management tools to accompany them.

For these automated systems to work effectively, they will need robust software that can withstand the difficult working conditions of warehouses, assembly lines, and distribution centers. A barcode integration that struggles to accurately read damaged or broken barcode images, for instance, won’t last very long in such an environment. The software powering automated systems must be able to function under a variety of conditions and be adaptable enough to overcome obstacles without constant oversight from on-site workers.

Unleash Your Supply Chain With Barcode Xpress

Building software capable of meeting the needs of a truly digital supply chain is no easy task. That’s especially true when it comes to integrating barcode reading capabilities into supply chain applications. With so many barcode formats in use, developers need an SDK with the ability to accurately detect, read, and write both common and uncommon barcode types used across all industries.

Accusoft’s Barcode Xpress is a multi-language barcode integration capable of reading and writing more than 30 different barcode types quickly and accurately. A truly robust SDK solution, Barcode Xpress leverages the imaging functionalities of ImagXpress to repair damaged orbroken barcodes that other readers are unable to read.

Speed

Barcode Xpress is capable of detecting and decoding multiple barcodes on a page at speeds of up to 1,000 pages per minute. It doesn’t matter where the barcode is located, what type of code it is, or how many are present. The control is able to read them regardless of orientation within milliseconds.

Accuracy

Every time Barcode Xpress detects a barcode, it not only provides the information encoded within the image, but also reports a confidence value to ensure high levels of accuracy. Damaged, broken, or poorly printed barcodes can also be scanned thanks to the SDK’s image processing capabilities. Black noise, white noise, erasures, low resolution, white line streaks, and other common barcode problems are reconstructed and scanned automatically to keep the supply chain moving.

Versatility

With the ability to detect, read, and write over 30 different barcode types, Barcode Xpress is available in multiple configurations for Windows and Linux-based operating systems. The SDK library supports 24-bit color images, 8-bit grayscale images, and 1-bit black and white images, as well as providing more than 80 additional image processing and editing functions thanks to its ImagXpress integration.

Experience Barcode Xpress Today

Easy to deploy and utilize, Barcode Xpress is a true all-in-one solution for desktop and web applications seeking barcode recognition capabilities. Just a few lines of code is all it takes to unlock the full potential of your supply chain technology.

Find out just how simple barcode integration can be with Barcode Xpress. Sign up today to download a free trial or talk to one of our SDK specialists today to learn more.