> For the complete documentation index, see [llms.txt](https://docs.arcware.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcware.cloud/unreal-engine-setup/using-the-arcware-pixel-streaming-template-project/generic-file-transfer-from-ue-to-frontend/arcware-cloud-and-websdk-integration.md).

# Arcware Cloud & WebSDK Integration

Generic file transfer from UE to Frontend

One of the strongest advantages of this blueprint setup is its native compatibility across the entire Arcware ecosystem. Because this function is built into the official Arcware Pixel Streaming Template, it is designed to work "out of the box" without requiring additional network configuration or security overrides.

## Full Compatibility Matrix

| **Feature**         | **Compatibility Status** | **Notes**                                                                                                                                                                                                            |
| ------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Arcware Share Links | Fully Compatible         | Share links (e.g., `share.arcware.cloud/...`) use a default frontend that is already programmed to listen for the "Screenshot" and "FileTransfer" JSON responses. No extra coding is required to trigger a download. |
| Arcware WebSDK      | Fully Compatible         | The WebSDK (versions 1.3.3+) includes built-in handlers for file transfers. Developers can easily hook into the `onResponse` callback to manage how files are saved or displayed in custom web interfaces.           |
| UE Versions         | 5.6 and Higher           | Optimized for the latest Pixel Streaming infrastructure (UE 5.6+ recommended for best performance).                                                                                                                  |

## Why use this with the WebSDK?

If you are building a custom frontend rather than using a standard share link, the Arcware WebSDK simplifies the process. It automatically handles the binary stream coming from your Unreal Engine instance.

* Ease of Use: You don't need to manually manage WebSockets. The WebSDK identifies the file type from the blueprint’s JSON response and handles the browser's "blob" creation.
* Customization: While share links will simply download the file, the WebSDK allows you to intercept the file. For example, you could show the screenshot in a "Gallery" UI element on your website before the user decides to save it.

{% hint style="info" %}
**Note:** WebSDK Updates: Always use the latest version of the [`@arcware-cloud/pixelstreaming-websdk`](/web-integration/new-websdk.md) via npm or yarn to ensure you have the most stable file-handling hooks.
{% endhint %}


---

# 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.arcware.cloud/unreal-engine-setup/using-the-arcware-pixel-streaming-template-project/generic-file-transfer-from-ue-to-frontend/arcware-cloud-and-websdk-integration.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.