The quick brown fox jumps over the lazy dog.Sharing User Generated Content is built upon the existing APIs and fundamentals introduced in Steam Cloud. The methods provide an easy way to share content that can easily be discovered by through the Steam Workshop or your own web application. All methods are SteamAPI callback methods and require proper callback handling to get the results of the API call.

How it works
The interface to share content is part of ISteamRemoteStorage.h along with the Steam Cloud functions. A shared item is an instance of a file in the Steam Cloud at the moment in time when it was shared and is assigned a PublishedFileId. If the cloud file is ever overwritten or removed, the PublishedFileId will still return the originally shared file. A user must update the existing published file to signify that the clouded content is ready for consumption again.

A PublishedFileId will always reference the metadata that describes the shared file including the UGCHandle_t to the content file, title, description of the submission, amongst other properties (see the RemoteStorageGetPublishedFileDetailsResult_t struct for complete list of properties). Accessing the shared files require the caller to call UGCDownload and UGCRead as described in the Steam Cloud documentation.

All files shared in this manner are indexed by the Steam Cloud and is discoverable through several mechanisms:
Enumerating all files submitted by a user (for example, browsing files that your friend has shared)
Discovering community submitted content through Steam Workshop
Web APIs to enumerate and view community submitted content (see Web API for more details on how to use Web APIs)
Once files are shared, consumers of the content can queue/mark the files and add them to a subscription list through the provided APIs. This will provide a way for the application to list the files of the user is interested in, download them through UGCDownload, and finally load the content.

Steam Workshop and enabling Workshop for your application
The Steam Workshop is the website hosted through Steam that enumerates shared content and allows users to vote and comment on the content visible through the community. By default, applications are not enabled to be publically visible in the Workshop. This prevents content not intended to be shared through the Steam Workshop portal from being visible unless specifically configured by a Steam Account Manager.

All content shared with PublishWorkshopFile can be enumerated through Web API calls to rendered on external sites.

To include the content generated by your application in the workshop, please contact your account manager.

Sharing UGC by publishing


Sharing User Generated Content is built upon the existing APIs and fundamentals introduced in Steam Cloud. The methods provide an easy way to share content that can easily be discovered by through the Steam Workshop or your own web application. All methods are SteamAPI callback methods and require proper callback handling to get the results of the API call.

How it works
The interface to share content is part of ISteamRemoteStorage.h along with the Steam Cloud functions. A shared item is an instance of a file in the Steam Cloud at the moment in time when it was shared and is assigned a PublishedFileId. If the cloud file is ever overwritten or removed, the PublishedFileId will still return the originally shared file. A user must update the existing published file to signify that the clouded content is ready for consumption again.

A PublishedFileId will always reference the metadata that describes the shared file including the UGCHandle_t to the content file, title, description of the submission, amongst other properties (see the RemoteStorageGetPublishedFileDetailsResult_t struct for complete list of properties). Accessing the shared files require the caller to call UGCDownload and UGCRead as described in the Steam Cloud documentation.

All files shared in this manner are indexed by the Steam Cloud and is discoverable through several mechanisms:
Enumerating all files submitted by a user (for example, browsing files that your friend has shared)
Discovering community submitted content through Steam Workshop
Web APIs to enumerate and view community submitted content (see Web API for more details on how to use Web APIs)
Once files are shared, consumers of the content can queue/mark the files and add them to a subscription list through the provided APIs. This will provide a way for the application to list the files of the user is interested in, download them through UGCDownload, and finally load the content.

Steam Workshop and enabling Workshop for your application
The Steam Workshop is the website hosted through Steam that enumerates shared content and allows users to vote and comment on the content visible through the community. By default, applications are not enabled to be publically visible in the Workshop. This prevents content not intended to be shared through the Steam Workshop portal from being visible unless specifically configured by a Steam Account Manager.

All content shared with PublishWorkshopFile can be enumerated through Web API calls to rendered on external sites.

To include the content generated by your application in the workshop, please contact your account manager.

Sharing UGC by publishing

Sharing User Generated Content is built upon the existing APIs and fundamentals introduced in Steam Cloud. The methods provide an easy way to share content that can easily be discovered by through the Steam Workshop or your own web application. All methods are SteamAPI callback methods and require proper callback handling to get the results of the API call.

How it works
The interface to share content is part of ISteamRemoteStorage.h along with the Steam Cloud functions. A shared item is an instance of a file in the Steam Cloud at the moment in time when it was shared and is assigned a PublishedFileId. If the cloud file is ever overwritten or removed, the PublishedFileId will still return the originally shared file. A user must update the existing published file to signify that the clouded content is ready for consumption again.

A PublishedFileId will always reference the metadata that describes the shared file including the UGCHandle_t to the content file, title, description of the submission, amongst other properties (see the RemoteStorageGetPublishedFileDetailsResult_t struct for complete list of properties). Accessing the shared files require the caller to call UGCDownload and UGCRead as described in the Steam Cloud documentation.

All files shared in this manner are indexed by the Steam Cloud and is discoverable through several mechanisms:
Enumerating all files submitted by a user (for example, browsing files that your friend has shared)
Discovering community submitted content through Steam Workshop
Web APIs to enumerate and view community submitted content (see Web API for more details on how to use Web APIs)
Once files are shared, consumers of the content can queue/mark the files and add them to a subscription list through the provided APIs. This will provide a way for the application to list the files of the user is interested in, download them through UGCDownload, and finally load the content.

Steam Workshop and enabling Workshop for your application
The Steam Workshop is the website hosted through Steam that enumerates shared content and allows users to vote and comment on the content visible through the community. By default, applications are not enabled to be publically visible in the Workshop. This prevents content not intended to be shared through the Steam Workshop portal from being visible unless specifically configured by a Steam Account Manager.

All content shared with PublishWorkshopFile can be enumerated through Web API calls to rendered on external sites.

To include the content generated by your application in the workshop, please contact your account manager.

Sharing UGC by publishing