# Proxy video files

In [LightNet ](/lightnet/lightnet-overview.md)configurations, it is desirable that the Primary and Editor servers playback files even when these files will not be actually displayed from these servers. That's because on these machines the users usually want to see all the content in the Viewport.

However, if all Primary and Editor servers tried to play all these video assets in full resolutions, the performance load would be too heavy. That's why we developed **Proxy video file feature**.

### Proxy video file naming

<div align="left"><figure><img src="/files/tTh0zFOwteN37VCMeAVO" alt=""><figcaption></figcaption></figure></div>

If a Video asset has **\_proxyN** or **\_prxN** in its name, LightAct knows it is a proxy file downscaled by a factor of N. This means the *Play Video* node before it passes the frame onwards, upscales it by the factor of N.

In the above image, for example, LightAct knows that:

* the original file is called *LightAct\_showreel\_published.mov*
* there is a proxy downscaled by 2, which, if it were played, is going to be upscaled by factor of 2
* and a proxy downscaled by 4, which, when played, is going to be upscaled by factor of 4.

<div align="left"><figure><img src="/files/1HDzNqouphAlDEsr6qg7" alt=""><figcaption></figcaption></figure></div>

The proxy status of a specific video asset is visible in its *Properties*.

{% hint style="info" %}
**Good to know**: How LightAct determines which server in a LightNet cluster should play the source, which server should play a proxy and which server shouldn't play a particular video asset at all is explained in [LightNet](/lightnet/lightnet-overview.md) chapter (specifically [here](https://docs.lightact.com/lightnet/server-workload-distribution#run-on-for-layers)).
{% endhint %}

{% hint style="info" %}
**Good to know**: if a server determines that it should be playing a proxy file and not the original one, it will always take the one that's been downscaled the most.

For example, if there are both \_proxy2 and \_proxy4 available, LightAct is going to play *\_*&#x70;roxy4.
{% endhint %}


---

# 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.lightact.com/video-playback/proxy-video-files.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.