> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/sdks/web-integrations/web-sdk-quick-guide.md).

# Web SDK

Embed KYC and identity verification flows in your web app with the ComplyCube Web SDK.

## Overview

The **ComplyCube Web SDK** is a lightweight JavaScript library that lets you embed identity verification (IDV) flows directly into your web applications. It provides a ready-made, user-friendly widget for capturing documents, selfies, and proof of address, while handling quality detection and fraud signals under the hood.

Use the Web SDK if you want to run verification flows inside your web app, instead of redirecting users to the [Hosted Solution](/documentation/sdks/web-integrations/hosted-solution-quick-guide.md).

## Benefits

The SDK offers several benefits:

* **Flexible integration**: Orchestrate full journeys with [workflows](/documentation/product-guides/compliance-studio/workflows.md) or configure individual stages (selfie, document).
* **Biometric checks**: Liveness via photo and video, with spoof detection.
* **Smart quality checks**: Real-time quality checks to reduce errors and ensure optimal input.
* **Custom branding**: Adapt colors, text, and logos to match your app.
* **Global-ready**: Multi-language support with localized UI labels. View [supported languages and locale codes](/documentation/sdks/supported-languages.md).

## Interactive demo

{% @arcade/embed url="<https://app.arcade.software/share/kjtci521jMvvMXDZIr7o>" flowId="kjtci521jMvvMXDZIr7o" fullWidth="false" %}

## Integration modes

The Web SDK can be integrated in two different ways, depending on your needs:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Workflow Integration</strong></mark></td><td>Use the Workflow Designer to build your customer KYC journey and simply load it through the SDK. This is the preferred option for most use cases.</td><td><strong>Recommended</strong></td><td><a href="/documentation/sdks/web-integrations/web-sdk-quick-guide/web-sdk-quick-guide.md">Workflow Integration</a></td></tr><tr><td><mark style="color:blue;"><strong>Check-Driven Integration</strong></mark></td><td>A lower-level approach where you directly control individual SDK screens and checks. It's best suited for advanced use cases.</td><td></td><td><a href="/documentation/sdks/web-integrations/web-sdk-quick-guide/web-sdk-quick-guide-1.md">Check-Driven Integration</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/sdks/web-integrations/web-sdk-quick-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.