> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Find and evaluate a template

> Find an Octoparse template by website or business need, then check its inputs, output fields, and sample results before running it.

Finding the right template starts with two questions: which website is the data from, and what data is needed? The instructions, required inputs, and output fields on each template page show whether it matches those requirements. A small test can then confirm the expected result before a larger collection begins.

<Card title="Open the template gallery" href="https://www.octoparse.com/template">
  Templates are organized by website and business category.
</Card>

## Find a template

### Search by website

When the data source is already known, the website or brand name is the most direct way to search the gallery. A single website may have several templates because each one is designed for different inputs and collection targets. For example, one Twitter template may accept a keyword and collect matching posts, while another may accept a profile URL and collect data from that Twitter profile.

The right template should match four parts of the requirement: the target website, the content to collect, the input you can provide, and the fields you expect in the output. The template title, description, input example, and output preview explain these differences.

### Browse by business need

Categories are useful when the business need or use case is clear, but the data source has not yet been decided. For example, a user looking to collect sales leads can open the **Lead Generation** category to see which sources are available and which templates can collect lead data from each source.

The templates and categories currently available are listed in the live [Template Gallery](https://www.octoparse.com/template).

## Check whether a template fits

The following details show whether a template fits the requirement:

| Check               | What to confirm                                                                                                             |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Website and content | The template supports the target website and the content you want to collect, such as posts, profiles, products, or reviews |
| Inputs              | The template accepts the URLs, keywords, locations, dates, or other information you can provide                             |
| Outputs             | The result includes the data fields you need                                                                                |
| Website access      | The template supports any region or login requirements for the target website                                               |
| Run mode            | The template can run through Local Extraction, Cloud Extraction, or both, depending on the supported mode                   |
| Access level        | The template is available to your Octoparse plan or account level                                                           |
| Sample result       | The example output matches the type and structure of data you expect                                                        |

More details are available in [Use templates across Octoparse interfaces](/docs/en/platform/templates/use-across-interfaces) for supported run modes and [Template pricing and plan access](/docs/en/platform/templates/pricing-and-plan-access) for account eligibility.

<Note>
  Templates for the same website can accept different inputs and return different fields. The instructions on each template page define the supported parameters and expected result.
</Note>

## What to check in a test run

A test run shows whether the template works with your actual inputs and target pages. The result should confirm that:

* The template accepts the provided input and completes the run successfully
* The output includes all required fields available on the target pages
* The template extracts all expected records from every page within the requested scope
* The field values in the output match the corresponding data on the source pages

## If no template matches

You can [download the Octoparse desktop app](https://www.octoparse.com/download) and use [Auto-detect](/docs/en/platform/auto-detect) to create a custom task. For a difficult or recurring requirement, you can also [request template development](/docs/en/platform/templates/custom-services); the Octoparse team will review the target website, required data, and intended use case before confirming whether to proceed.

## Next steps

<Columns cols={2}>
  <Card title="Use a template" href="/docs/en/platform/templates/use-across-interfaces">
    Learn which Octoparse interface fits each workflow.
  </Card>

  <Card title="Troubleshoot a template" href="/docs/en/platform/templates/troubleshooting">
    Understand the causes of empty, incomplete, or unexpected results.
  </Card>
</Columns>