See all results >
Download 30-Day Trial
Table of contents

Scan Single-Page Documents with Mobile Document Scanner

Read the Introduction for common use cases, an overview of the SDK architecture, and system requirements.

Dynamsoft’s Mobile Document Scanner JavaScript Edition (MDS) is a web SDK designed for scanning single-page documents. MDS captures images of the documents and enhances their quality to professional standards, making it an ideal tool for mobile document scanning.

See it in action with the Mobile Document Scanner Demo.

This guide walks you through building a web application that scans single-page documents using MDS with pre-defined configurations.

License

Get a Trial License

You can request a trial license for Mobile Document Scanner here:

We are unable to deliver to the email address provided. Please try a different one.

One Click to Request a 30-Day Trial License

or continue with a work email

* Business Email Address
* First Name
* Last Name
* Company Name
* Phone Number
Generate a License

The license will be sent to your email immediately.

Submit

The license will be sent to your email immediately.

The trial license can be renewed twice for a total of two months of free access.

Get a Full License

Contact us to purchase a full license.

Quick Start

To use the Mobile Document Scanner, first obtain its library files. You can acquire them from one of the following sources:

  1. GitHub – contains the source files for the MDS SDK, which can be compiled into library files.
  2. npm – provides precompiled library files via npm for easier installation.
  3. CDN – delivers precompiled library files through a CDN for quick and seamless integration.

You can choose one of the following methods to set up a Hello World page:

  1. Build from source – download the source files from GitHub and compile the library files yourself.
  2. Use precompiled scripts – use the precompiled resource scripts from npm or the CDN for a quicker setup.
  3. Self-host resources - self-host both MDS and its dependencies on your web server.
Build from Source

Build from Source

This method retrieves all MDS source files from its GitHub Repository, compiles them into a distributable package, and then runs a ready-made Hello World sample page included in the repository:

  1. Download MDS from GitHub as a compressed folder.

  2. Extract the contents of the archive, and open the extracted directory in a code editor.

  3. Set your license key in the Hello World sample:
    1. Open the Hello World sample at /samples/hello-world.html.
    2. Search for "YOUR_LICENSE_KEY_HERE", then replace it with your actual license key.

  4. In the terminal, navigate to the project root directory and run the following to install project dependencies:

     npm install

  5. After installing dependencies, build the project by running:

     npm run build

  6. Start the local server by running the following to serve the project locally:

     npm run serve

    Once the server is running, open the application in a browser using the address provided in the terminal output after running npm run serve.

    See the server configuration details in /dev-server/index.js.

Use Precompiled Script

Use Precompiled Scripts

We publish MDS library files on npm to make them simple to reference from a CDN.

To use the precompiled script, simply include the following URL in a <script> tag:

<script src="https://cdn.jsdelivr.net/npm/dynamsoft-document-scanner@1.3.1/dist/dds.bundle.js"></script>

Below is the complete Hello World sample page that uses this precompiled script from a CDN.

The code is identical to the /samples/hello-world.html file mentioned in the Build from Source section, except for the script source.

Remember to replace "YOUR_LICENSE_KEY_HERE" with your actual license key.

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>Mobile Document Scanner - Hello World</title> <script src="https://cdn.jsdelivr.net/npm/dynamsoft-document-scanner@1.3.1/dist/dds.bundle.js"></script> </head> <body> <h1 style="font-size: large">Mobile Document Scanner</h1> <div id="results"></div> <script> const resultContainer = document.querySelector("#results"); // Instantiate a Document Scanner Object const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key }); (async () => { // Launch the scanner and wait for the result const result = await documentScanner.launch(); console.log(result); // Clear the result container and display the scanned result as a canvas if (result?.correctedImageResult) { resultContainer.innerHTML = ""; // Clear placeholder content const canvas = result.correctedImageResult.toCanvas(); resultContainer.appendChild(canvas); } else { resultContainer.innerHTML = "<p>No image scanned. Please try again.</p>"; } })(); </script> </body> </html>

To run the sample, create a new file called hello-world.html, then copy and paste the code above into the file. Next, serve the page directly by deploying it to a server.

If you are using VS Code, a quick and easy way to serve the project is using the Live Server (Five Server) VSCode extension. Simply install the extension, open the hello-world.html file in the editor, and click “Go Live” in the bottom right corner of the editor. This will serve the application at http://127.0.0.1:5500/hello-world.html.

Alternatively, you can use other methods like IIS or Apache to serve the project, though we skip those here for brevity.

Self-Host Resources

Self-Host Resources

By default, the MDS library (whether pre-compiled or self-compiled) fetches resource files (Dynamsoft node packages dynamsoft-capture-vision-bundle and dynamsoft-capture-vision-data, and an HTML UI template) from CDNs. Self-hosting library resources gives you full control over hosting your application. Rather than using CDNs to serve these resources, you can instead host these resources on your own servers to deliver to your users directly when they use your application. You can also use this option to host MDS fully offline by pointing to local resources.

Download Resources

First, download a copy of the library:

  1. Download MDS from GitHub as a compressed folder.

  2. Extract the contents of the archive, and open the extracted directory in a code editor.

  3. Set your license key in the Hello World sample:

    1. Open the Hello World sample at (/samples/hello-world.html).

    2. Search for "YOUR_LICENSE_KEY_HERE", then replace it with your actual license key.

  4. In the terminal, navigate to the project root directory and run the following to install project dependencies:

     npm install

Point to Resources

The library uses engineResourcePaths to locate required Dynamsoft node dependencies by pointing to the location of the resources on your web server. The library also uses scannerViewConfig.cameraEnhancerUIPath similarly to set the path for the HTML UI template of the ScannerView. The included sample server at dev-server/index.js can serve local files for this demonstration. Later steps will place both the node dependencies and the HTML template in the local dist directory. Therefore, set engineResourcePaths in the MDS constructor to point to the local dist directory (along with setting your license key, and all other configurations):

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", scannerViewConfig: { cameraEnhancerUIPath: "dist/document-scanner.ui.html", // Use the local file }, engineResourcePaths: { rootDirectory: "dist/libs/" }, });

API Reference:

Modify the Build Script

Update the scripts section in package.json to automatically copy resources to the output dist directory during the build process. This script gets the dynamsoft-capture-vision-data package, and moves both dynamsoft-capture-vision-data and dynamsoft-capture-vision-bundle to dist/libs/, which is where we set the resource directory to.

"scripts": { "serve": "node dev-server/index.js", "build": "rollup -c && npm run get-libs", "get-libs": "npm install --no-save dynamsoft-capture-vision-data dynamsoft-capture-vision-bundle && npx mkdirp /dist/libs && npx cpx 'node_modules/dynamsoft-*/**/*' dist/libs/ --dereference, "build:production": "rollup -c --environment BUILD:production" },

Serve the Resources

The included sample server at dev-server/index.js needs an extra statement to serve the resources. Include this line:

app.use("/dist/libs", express.static(path.resolve(__dirname, "../dist/libs")));

Build the Project

Build the project by running:

npm run build

Serve the Project Locally

Start the local development server by running:

npm run serve

Once the server is running, open the application in a browser using the address provided in the terminal output.

Serve over HTTPS

Place the dist directory onto your web server for to serve the web application. When deploying your web application for production, you must serve it over a secure HTTPS connection. We require this for the following reasons:

  1. Browser Security Restrictions – Most browsers only allow access to camera video streams in a secure context.

    Some browsers like Chrome may grant access to camera video streams for http://127.0.0.1, http://localhost, or even pages opened directly from the local file system (file:///...). This can be helpful during development and testing.

  2. Dynamsoft License Requirements – A secure context is required for Dynamsoft licenses to function properly.

Set MIME Type

Certain legacy web application servers may lack support for the application/wasm mimetype for .wasm files. To address this, you have two options:

  1. Upgrade your web application server to one that supports the application/wasm mimetype.
  2. Manually define the mimetype on your server by setting the MIME type for .wasm as application/wasm. This allows the user’s browser to correctly processes resource files. Different web servers have their own way of configuring the MIME type. Here are instructions for Apache, IIS, and NGINX.

Resource Caching

The wasm resource files are relatively large and may take quite a few seconds to download. We recommend setting a longer cache time for these resource files to maximize the performance of your web application using the Cache-Control HTTP header. For example, use the max-age directive to cache resources for a specified time in seconds:

Cache-Control: max-age=31536000

Reference: Cache-Control

Hello World Sample Explained

Here we walk through the code in the Hello World sample to explain its function and usage.

You can also view the full code by visiting the MDS JS Hello World Sample on Github.

Reference MDS

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>Mobile Document Scanner - Hello World</title> <script src="../dist/dds.bundle.js"></script> <!--Alternatively, reference the script from CDN <script src="https://cdn.jsdelivr.net/npm/dynamsoft-document-scanner@1.3.1/dist/dds.bundle.js"></script> --> </head> </html>

In this step, we reference MDS with a relative path to the local file in the <head> section of the HTML.

<script src="../dist/dds.bundle.js"></script>

Alternatively, you can reference the script hosted on a CDN, for example, on JSDelivr:

<script src="https://cdn.jsdelivr.net/npm/dynamsoft-document-scanner@1.3.1/dist/dds.bundle.js"></script>

MDS wraps all its dependency scripts, so a MDS project only needs to include MDS itself as a single script. No additional dependency scripts are required.

Even if you reference the script itself locally, MDS still defaults to loading supporting resources like .wasm engine files from the CDN at runtime. If you require a fully offline setup, follow the quick start instructions to self-host resources.

Instantiate MDS

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key });

API Reference:

This step creates the MDS UI, which by default occupies the entire visible area of the browser window when launched. If needed, you can restrict the UI to a specific container. For more details, refer to Confine DocumentScanner UI to a Specific Container.

Instantiating the DocumentScanner requires a valid license key.

Launch MDS

const result = await documentScanner.launch();

API Reference:

This step launches the user into the document scanning workflow, beginning in the DocumentScannerView, where they can scan a document using one of three methods:

  • Option 1: Manually scan by pressing the shutter button.
  • Option 2: Enable “Smart Capture” - the scanner will automatically capture an image once a document is detected.
  • Option 3: Enable “Auto Crop” - the scanner will automatically capture an image, detect the document, and crop it out of the video frame.

For Options 1 & 2: The user is directed to DocumentCorrectionView to review detected document boundaries and make any necessary adjustments before applying corrections. Afterward, they proceed to DocumentResultView.

For Option 3: The DocumentCorrectionView step is skipped. Image correction is applied automatically, and the user is taken directly to DocumentResultView.

In DocumentResultView, if needed, the user can return to DocumentCorrectionView to make additional adjustments or press “Re-take” to restart the scanning process.

Display the Result

The workflow returns a scanned image object of type CorrectedImageResult. To display the scanned result image, we use a <div> in the <body>:

<body> <h1 style="font-size: large">Mobile Document Scanner</h1> <div id="results"></div> </body>

API Reference:

The following code clears the result container and displays the scanned result as a canvas:

if (result?.correctedImageResult) { resultContainer.innerHTML = ""; const canvas = result.correctedImageResult.toCanvas(); resultContainer.appendChild(canvas); } else { resultContainer.innerHTML = "<p>No image scanned. Please try again.</p>"; }

Custom Usage

This section builds on the Hello World sample to demonstrate how to configure MDS, typically by adjusting the DocumentScannerConfig object.

DocumentScannerConfig Overview

DocumentScannerConfig is the primary configuration object for customizing MDS. It includes the following properties:

  1. license - the license key.
  2. container - the HTML container for the entire workflow. If not specified (like in the Hello World Sample), one is created automatically.
  3. showCorrectionView - toggles DocumentCorrectionView in the scanning workflow.
  4. showResultView - toggles DocumentResultView in the scanning workflow.
  5. scannerViewConfig - configures the main scanner view with the following properties:
    1. container - the HTML container for the DocumentScannerView.
    2. cameraEnhancerUIPath - path to the UI definition file (.html) for the DocumentScannerView.
    3. enableAutoCropMode - sets the default value of Auto-Crop upon entering the DocumentScannerView.
    4. enableSmartCaptureMode - sets the default state of Smart Capture upon entering the DocumentScannerView.
    5. scanRegion - sets the scan region within the document scanning viewfinder.
    6. minVerifiedFramesForSmartCapture - sets the minimum number of video frames to verify detected document boundaries on Smart Capture mode. Higher frame counts lead to higher confidence at the cost of discarding results.
    7. showSubfooter - toggles the visibility of the mode selector menu.
    8. showPoweredByDynamsoft - sets the visibility of the Dynamsoft branding message.
  6. correctionViewConfig - configures the DocumentCorrectionView.
    1. container - the HTML container for the DocumentCorrectionView.
    2. toolbarButtonsConfig - configures the appearance and labels of the buttons for the DocumentCorrectionView UI.
    3. onFinish - handler called when the user clicks the “Apply” button.
  7. resultViewConfig - configures the result view with the following properties:
    1. container - the HTML container for the DocumentResultView.
    2. toolbarButtonsConfig - configures the appearance and labels of the buttons for the DocumentResultView UI.
    3. onDone - handler called when the user clicks the “Done” button.
    4. onUpload - handler called when the user clicks the “Upload” button.
  8. templateFilePath - path to a Capture Vision template for scanning configuration; typically not needed as the default template is used.
  9. utilizedTemplateNames- template names for detection and correction. Typically not needed as the default template is used.
  10. engineResourcePaths - paths to extra resources such as .wasm engine files.

Furthermore, we explore two main methods of customizing MDS with DocumentScannerConfig:

  1. Workflow Customization: through container definitions.
  2. View-Based Customization: through configuration objects.

The customization examples below build on the Hello World code from the previous section. The only change required is adjusting the constructor argument.

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key // Add more arguments });

Workflow Customization

In the Hello World sample, we use the complete workflow with minimum configuration:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key }); // Launch the scanner and wait for the result const result = await documentScanner.launch();

In this case, MDS automatically creates container elements for its Views. In this section we discuss a few ways to adjust the MDS workflow.

Example 1: Confine DocumentScanner UI to a Specific Container

As long as the DocumentScanner container is assigned, MDS confines its Views within that container.

Containers assigned to its constituent Views will be ignored.

<div id="myDocumentScannerContainer" style="width: 80vw; height: 80vh;"></div> 
const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key container: document.getElementById("myDocumentScannerContainer"), // Use this container for the full workflow scannerViewConfig: { container: document.getElementById("myDocumentScannerViewContainer"), // This container is ignored }, });

API Reference:

Example 2: Only Show DocumentScannerView

If you do not need either the DocumentResultView or DocumentCorrectionView in your workflow (for example, if you do not want your user to manually alter the detected document boundaries), you can hide the views with the following configuration properties like so:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key showResultView: false, showCorrectionView: false, });

API Reference:

Example 3: Specify Individual View Containers

If the configuration object provide containers for the DocumentScannerView, DocumentResultView, and DocumentCorrectionView, but does not provide the DocumentScanner container, then MDS renders the full workflow using these three containers.

<div id="myDocumentScannerViewContainer" style="width: 80vw; height: 80vh"></div> <div id="myDocumentCorrectionViewContainer" style="width: 80vw; height: 80vh"></div> <div id="myScanResultViewContainer" style="width: 80vw; height: 80vh"></div> 
const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key scannerViewConfig: { container: document.getElementById("myDocumentScannerViewContainer"), }, correctionViewConfig: { container: document.getElementById("myDocumentCorrectionViewContainer"), }, resultViewConfig: { container: document.getElementById("myScanResultViewContainer"), }, });

API Reference:

Example 4: Scan Static Image Directly

To scan an image file directly without displaying the DocumentScannerView UI at all, you can pass a File object to launch(). As an example, select an image file from the local disk:

<input type="file" id="initialFile" accept="image/png,image/jpeg" />

Then get the input file as a File object, and pass that file object to launch() MDS with:

document.getElementById("initialFile").onchange = async function () { const files = Array.from(this.files || []); if (files.length) { const result = await documentScanner.launch(files[0]); console.log(result); // Clear the result container and display the scanned result as a canvas if (result?.correctedImageResult) { resultContainer.innerHTML = ""; // Clear placeholder content const canvas = result.correctedImageResult.toCanvas(); resultContainer.appendChild(canvas); } else { resultContainer.innerHTML = "<p>No image scanned. Please try again.</p>"; } } };

This hides the DocumentScannerView UI entirely and brings up the DocumentCorrectionView as the first view, after having detected document boundaries on the static image. The user can proceed through the rest of the workflow and further alter the document boundaries, re-take another image (to open up the DocumentScannerView), etc.

launch() can accept images or PDFs. If launching with a PDF, MDS will only process the first page.

You can completely disable all UI and use MDS to scan a file completely statically by hiding both the DocumentCorrectionView and the DocumentResultView in example 2.

Example 5: Configure Scan Modes

The Document Scanner View comes with three scan modes:

  1. Border Detection
  2. Auto-Crop
  3. Smart Capture

By default, Border Detection mode is enabled upon entering the Scanner View, while the other two are turned off by default. The user can then enable them by clicking their respective icons in the scanning mode sub-footer. From the DocumentScannerViewConfig interface, you can:

  1. Set the default state of Auto-Crop mode with enableAutoCropMode
  2. Set the default state of Smart Capture mode with enableSmartCaptureMode
  3. Set the visibility of the scanning mode sub-footer with showSubfooter

Border Detection Mode is always enabled upon the Scanner View, and the scanning sub-footer is visible by default.

For example, the following config enables all three scanning modes and hides the scanning mode sub-footer to prevent the viewer from changing or viewing the scanning modes:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key scannerViewConfig: { enableAutoCropMode: true, enableSmartCaptureMode: true, showSubfooter: false, }});

API Reference:

View-Based Customization

In addition to modifying the workflow, you can customize individual Views with configuration options for UI styling, button settings, and event handling.

DocumentScannerView Configuration

Customizing the DocumentScannerView UI

You can extensively customize the DocumentScannerView by editing its HTML template. Consider the following properties of the DocumentScannerViewConfig used for customizing the DocumentScannerView:

interface DocumentScannerViewConfig { container?: HTMLElement; templateFilePath?: string; cameraEnhancerUIPath?: string; }

Of these three properties, we focus on cameraEnhancerUIPath. Here we omit container, as we cover it in Workflow Customization, and we omit templateFilePath, as it refers to the DCV template file that configures document boundary detection algorithms.

If the performance of MDS does not meet your needs, you may require an algorithm template customized for your usage scenario for better results. Please contact our experienced Technical Support Team to discuss your requirements. We can tailor a suitable template for you, which you can then apply by updating templateFilePath.

cameraEnhancerUIPath points to a file hosted on the jsDelivr CDN by default (see Self-Host Resources: Point to Resources): https://cdn.jsdelivr.net/npm/dynamsoft-document-scanner@1.3.1/dist/document-scanner.ui.html.

This file defines the UI for DocumentScannerView. Since files on the CDN cannot be modified directly, you must to use a local version to customize the UI. cameraEnhancerUIPath specifies the file path to this local version of the UI.

Steps to Customize the UI for DocumentScannerView

  1. Follow the instructions in Build from Source to obtain the source files for MDS.

  2. Edit the existing /src/document-scanner.ui.html to apply your customizations.

  3. Build the project to generate the updated file in /dist/document-scanner.ui.html:

     npm run build

  4. Update the configuration to use the local file instead of the CDN version:

     const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace with your actual license key scannerViewConfig: { cameraEnhancerUIPath: "../dist/document-scanner.ui.html", // Use the local file }, });

API Reference:

Customizing the Scanning Region

We can customize the scanning region in the viewfinder with the scanRegion property in the configuration object. You may want to do this if you want to only scan your document in a specific sub-region in the viewfinder.

interface ScanRegion { ratio: { width: number; height: number; }; regionBottomMargin: number; // Bottom margin calculated in pixel style: { strokeWidth: number; strokeColor: string; }; }

API Reference:

ScanRegion

Here is how ScanRegion applies its settings to the viewfinder:

  1. Use the ratio property to set the height-to-width of the rectangular scanning region, then scale the rectangle up to fit within the viewfinder.
  2. Translate the rectangular up by the number of pixels specified by regionBottomMargin.
  3. Create a visual border for the scanning region boundary on the viewfinder with a given stroke width in pixels, and a stroke color.

For example:

scanRegion { ratio: { width: 2; height: 3; }; regionBottomMargin: 20; style: { strokeWidth: 3; strokeColor: "green"; }; }

This creates a scan region with a height-to-width ratio of 3:2, translated upwards by 20 pixels, with a green, 3 pixel-wide border in the viewfinder.

DocumentCorrectionView Configuration

The following configuration interface customizes the DocumentCorrectionView:

interface DocumentCorrectionViewConfig { container?: HTMLElement; toolbarButtonsConfig?: DocumentCorrectionViewToolbarButtonsConfig; onFinish?: (result: DocumentScanResult) => void; }

This section omits the container option, as we cover it in the Workflow Customization section. Below we discuss the other two properties.

Styling DocumentCorrectionView Buttons

The toolbarButtonsConfig property (of type DocumentCorrectionViewToolbarButtonsConfig) customizes the appearance and functionality of the UI buttons. Here is its definition:

type ToolbarButtonConfig = Pick<ToolbarButton, "icon" | "label" | "isHidden">; interface DocumentCorrectionViewToolbarButtonsConfig { fullImage?: ToolbarButtonConfig; detectBorders?: ToolbarButtonConfig; apply?: ToolbarButtonConfig; }

We can use it to change the icon and label of each of the three buttons individually or even hide the buttons. Below is an example that sets a custom label and image icon for the “Detect Borders” button and hides the “Full Image” button:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key correctionViewConfig: { toolbarButtonsConfig: { fullImage: { isHidden: true, }, detectBorders: { icon: "path/to/new_icon.png", // Change to the actual path of the new icon label: "Custom Label", }, }, }, });

API Reference:

Customizing Apply Button Callback

The onFinish callback triggers upon having applied the user’s corrections. For example, the code below displays the corrected image in a resultContainer after the user clicks “Apply”:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key correctionViewConfig: { onFinish: (result) => { const canvas = result.correctedImageResult.toCanvas(); resultContainer.appendChild(canvas); }, }, });

API Reference:

DocumentResultView Configuration

Consider toolbarButtonsConfig, onDone and onUpload from the DocumentResultViewConfig configuration interface to customize the DocumentResultView:

interface DocumentResultViewConfig { container?: HTMLElement; toolbarButtonsConfig?: DocumentResultViewToolbarButtonsConfig; onDone?: (result: DocumentResult) => Promise<void>; onUpload?: (result: DocumentResult) => Promise<void>; }
Styling DocumentResultView Buttons

The toolbarButtonsConfig property, of type DocumentResultViewToolbarButtonsConfig, customizes the appearance and functionality of the UI buttons. Here is its definition:

type ToolbarButtonConfig = Pick<ToolbarButton, "icon" | "label" | "isHidden">; interface DocumentResultViewToolbarButtonsConfig { retake?: ToolbarButtonConfig; correct?: ToolbarButtonConfig; share?: ToolbarButtonConfig; upload?: ToolbarButtonConfig; done?: ToolbarButtonConfig; }

This property ca change the icon and label of each of the three buttons individually in the DocumentResultView or even *hide the buttons. Below is an example that sets a custom label and image icon for the “Retake” button, and hides the “Share” button:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key resultViewConfig: { toolbarButtonsConfig: { retake: { icon: "path/to/new_icon.png", // Change to the actual path of the new icon label: "Custom Label", }, share: { isHidden: true, }, }, }, });

API Reference:

Customizing the “Done” Button Callback

The onDone callback triggers upon pressing the “Done” button. For example, the code below displays the result image in a resultContainer after the user clicks “Done”:

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key resultViewConfig: { onDone: async (result) => { const canvas = result.correctedImageResult.toCanvas(); resultContainer.appendChild(canvas); }, }, });

API Reference:

Customizing the “Upload” Button

The onUpload callback triggers upon pressing the “Upload” button. Note that the “Upload” button only appears if a callback function is defined for onUpload; the button remains hidden otherwise.

The following example demonstrates how to upload the result image to a server:

The following code applies if you follow the steps in Build from Source and use the predefined express server setup. The scanned image uploads directly to the dev server as “uploadedFile.png”. See the server configuration details in /dev-server/index.js for more details.

const documentScanner = new Dynamsoft.DocumentScanner({ license: "YOUR_LICENSE_KEY_HERE", // Replace this with your actual license key resultViewConfig: { onUpload: async (result) => { const host = window.location.origin; const blob = await result.correctedImageResult.toBlob(); // Create form data const formData = new FormData(); formData.append("uploadFile", blob, "uploadedFile.png"); // Upload file const response = await fetch( `${host}/upload`, // Change this to your actual upload URL { method: "POST", body: formData, }, ); }, }, });

API Reference:

Next Step

MDS is a fully functional, ready-to-use single page scanning SDK with built-in UI layouts. There are two options which extend the features of MDS:

  1. To scan multi-page documents as PDFs, please contact Dynamsoft Support for further information.

  2. For multi-page and multi-document processing, as well as advanced editing features, we developed Mobile Web Capture (MWC). Read on to learn how to use this web-based wrapper SDK in the Mobile Web Capture User Guide.

This page is compatible for:

Is this page helpful?

YesYes NoNo

In this article: