> For the complete documentation index, see [llms.txt](https://docs.hology.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hology.app/release/distribution/publishing-to-steam.md).

# Publishing to Steam

Steam is a digital distribution platform for PC gaming that offers game developers access to a vast global audience, revenue opportunities through various pricing models, integration with Steamworks for feature-rich gameplay experiences, community engagement tools, early access and beta testing options, promotional opportunities, protection against piracy, analytics and data insights, and a revenue-sharing model. It's a comprehensive ecosystem that can significantly enhance a game's reach and success.

Publishing a game made with Hology is like publishing any HTML5 game to Steam. You first need to package it into an executable application that can be installed on a PC. A popular choice for this is Electron.js. Please refer to the Electron.js docs for how to package your application.

{% embed url="<https://www.electronjs.org/docs/latest/>" %}

After you have your game packaged, you need to integrate Steamworks. You can read more about how that can be done in this guide.

{% embed url="<https://liana.one/integrate-electron-steam-api-steamworks>" %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.hology.app/release/distribution/publishing-to-steam.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.