> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/device-related-questions/hvideo-vs-evideo-commands.md).

# HVIDEO vs EVIDEO commands

Choose video retrieval source: HVIDEO pulls lower-quality sub-stream footage faster, while EVIDEO extracts higher-quality SD card video with more data usage

## Question

What are the differences between HVIDEO and EVIDEO commands (JC400/JC261)?

## Answer

Both commands are used to request video files from the server. When you search for a specific video clip, either command can be used to retrieve it.

However, the key difference is where the video is sourced from:

* **HVIDEO** retrieves the video from the camera's **sub-stream**, which is encoded at a lower quality. Additionally, due to recent firmware updates (FW + 1.6.3), the number of days available through the sub-stream has been reduced.
* **EVIDEO** extracts the video **directly from the SD card**, which provides higher video quality but may require more data consumption during upload.

In short, **HVIDEO** offers faster, lower-quality retrieval from the sub-stream, while **EVIDEO** provides higher-quality footage directly from the SD card at the cost of increased data usage.


---

# 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://navixy.com/docs/qna/device-related-questions/hvideo-vs-evideo-commands.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.