# Displaying the CLI results in an HTML format using the Snyk-to-HTML feature

When using Snyk Code via the CLI, the test results are displayed in a concise text format in the terminal, and they do not include the Data Flow and Fix Analysis information that is available for each discovered issue in the Web UI. The Snyk-to-HTML feature enables you to convert these text results into an HTML file, and to display the vulnerability findings along with their Data Flow and Fix Analysis information as an HTML Report in a browser.

For example:

When using Snyk Code via the CLI for testing a certain repository, the vulnerability findings are displayed in the terminal in the following way:

![](/files/1x1fp8nky2l3hgWGKwkB)

When converting the CLI textual findings into HTML using the Snyk-to-HTML feature, the following **HTML Report** is generated:

![](/files/Jq4Wb7SsHeT9IQV2Kws5)

The Snyk-to-HTML feature uses the Snyk-to-HTML tool, which you need to download and install before running the snyk-to-html command. Then, you should test your source code with Snyk Code via the CLI, and export the results to a JSON or SARIF file. The snyk-to-html command takes the information on the test results from the JSON/SARIF file, and convert it to an HTML file that can be displayed in a browser.

**The workflow of using the Snyk-to-HTML feature is as follows:**

1\. [Installing the Snyk-to-HTML tool via the CLI](/~/changes/m2hJeDrttXy2N83AnRjM/scan-application-code/snyk-code/cli-for-snyk-code/displaying-the-cli-results-in-an-html-format-using-the-snyk-to-html-feature/installing-the-snyk-to-html-tool.md).

2\. [Running the Snyk Code test of your repository in the CLI, and exporting the results to a JSON/SARIF file](/~/changes/m2hJeDrttXy2N83AnRjM/scan-application-code/snyk-code/cli-for-snyk-code/displaying-the-cli-results-in-an-html-format-using-the-snyk-to-html-feature/running-the-snyk-to-html-command.md#running-the-snyk-to-html-feature-in-several-steps).

3\. [Running the snyk-to-html command in the CLI, and generating an HTML file with the test results](/~/changes/m2hJeDrttXy2N83AnRjM/scan-application-code/snyk-code/cli-for-snyk-code/displaying-the-cli-results-in-an-html-format-using-the-snyk-to-html-feature/running-the-snyk-to-html-command.md#running-the-snyk-to-html-feature-in-several-steps).

**Note**: [Steps 2-3 above can be done in one command line](/~/changes/m2hJeDrttXy2N83AnRjM/scan-application-code/snyk-code/cli-for-snyk-code/displaying-the-cli-results-in-an-html-format-using-the-snyk-to-html-feature/running-the-snyk-to-html-command.md#running-the-snyk-to-html-command-in-one-step).

4\. [Opening the generated HTML file in a browser to view the discovered vulnerabilities](/~/changes/m2hJeDrttXy2N83AnRjM/scan-application-code/snyk-code/cli-for-snyk-code/displaying-the-cli-results-in-an-html-format-using-the-snyk-to-html-feature/viewing-the-html-results.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.snyk.io/~/changes/m2hJeDrttXy2N83AnRjM/scan-application-code/snyk-code/cli-for-snyk-code/displaying-the-cli-results-in-an-html-format-using-the-snyk-to-html-feature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
