> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/layers-ocgs/samples.md).

# JavaScript samples for working with PDF layers

Explore JavaScript samples for manipulating PDF layers. Learn to extract layer info, show/hide specific layers, and work with color separation. Enhance your PDF handling using web. The Apryse Web SDK

#### Layer separation

Shows how to get each layer's information. You can also show/hide specific layers.

<a href="https://sdk.apryse.com/samples/web/samples/pdf-manipulation/layer-separation/" class="button primary">Launch Demo</a><a href="/web/get-started/samples/layer-separation.md" class="button primary">View Source Code</a>

#### Color separation

Shows how to get each color's information. You can also show/hide specific colors.

<a href="https://sdk.apryse.com/samples/web/samples/pdf-manipulation/color-separation/" class="button primary">Launch Demo</a><a href="/web/get-started/samples/color-separation.md" class="button primary">View Source Code</a>

## Full API

{% hint style="info" %}
[Full API](/web/what-is-webviewer/full-api.md) is mainly used for PDF processing situations that are not featured using the Standard API. The preferred recommendation is to use the Standard API to address your situation when possible. Standard API is easy to use, loaded by default, and performs best for most situations.
{% endhint %}

#### PDFLayers

This sample demonstrates how to create PDF layers (also known as Optional Content Groups - OCGs). The sample also shows how to extract and render PDF layers.

<a href="https://sdk.apryse.com/samples/web/samples/full-apis/PDFLayersTest/" class="button primary">Launch Demo</a><a href="/web/get-started/samples/pdflayerstest.md" class="button primary">View Source Code</a>


---

# 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.apryse.com/web/layers-ocgs/samples.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.