Foundry Virtual Tabletop has a wide array of options for asset creators. This article seeks to provide useful information for musicians, artists, and other content creators who wish to create image or sound assets for use in Foundry, be it Token art, maps, environments, icons, sound effects, music, or any other media content.
Media Asset Creation
When creating media files for use in Foundry, file compression and file quality are generally the two important aspects that must be balanced. Considering your options is especially important when taking into account that each player connected to a Foundry server will need to be sent the file for each type of media over their connection. With more players, or less bandwidth, smaller media formats and other methods of compression may be necessary.
General Asset Guidelines
When designing for use in Foundry, ensure the name of your file properly reflects its intended use. It is good practice to differentiate between various versions of a file by name, so those using the assets can quickly identify which one they intend to use.
Since Foundry VTT works as a web server, you should be sure to use directory and file names which conform to web file and URL encoding conventions. You should generally avoid using spaces or special characters as these are likely to cause issues when serving your content. See the Google URL Guidelines for more detail.
Generating image assets for Foundry carries with it some best practices which can help to optimize your content for distribution. The recommendations change slightly whether you're creating Tokens, Tiles, or Maps for Scenes.
Foundry supports the following formats for image files:
.jpg, .jpeg, .png, .svg, .webp.
Image Design Best Practices
When approaching image design for Foundry it's usually best to keep in mind some general best practices for images to be served on a website.
Take note of a common misconception that DPI or PPI of an image defines its quality for VTT use. While this is true for print media, Foundry VTT does not reference the DPI or PPI of an image, but uses the pixel size of the image and the number of pixels per grid space. Pixels-per-square is synonymous with PPI (only) in cases where the map is printed at 1 inch per grid space.
How compatible does the image need to be?
The current best-in-class image file format for Foundry VTT usage is WebP which achieves the best quality-to-size ratio of any image format with lower file-sizes than JPEG but comparable quality while also supporting transparency like PNG.
While WebP produces the best results, it does have less compatibility as Safari and IOS users will not be able to use WebP images. Note that Safari is not officially supported for Foundry VTT, so if designing specifically for Foundry, WebP is a great choice.
WebP uses a more complex algorithm for compression which requires more work for the client CPU. Generally this trade-off is worth it, to reduce network transit in favor of more utilization of the client PC. The same holds true for audio codecs like OGG.
Does the image need transparency?
If you are designing a background map, there's a very good chance that you don't require transparency for your image, in which case rendering in jpg will provide a significant gain in filesize. For distribution to users, rendering exported JPG files at or slightly above 80% quality is usually sufficient. If you require transparency, however, your choices are limited to webp, png, and svg.
SVG for Simple or Geometric Images
For images which do not require a lot of visual complexity, SVG (Scalable Vector Graphics) can also be used which will feature tiny file-sizes, support for transparency, can be easily animated, and can be scaled to any size without noticeable loss of quality.
Consider using SVGs if you are making tiles, tokens, or icons for use in foundry that would benefit from transparency and scaling, but do not require extremely complex colour depth and detail.
In order to use a SVG image on a WebGL canvas, the SVG document must be given an explicit default width and height in its markup, for example:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" width="512" height="512">
When designing Token assets for use in foundry it is best to take into account overall file size and quality. Tokens should be provided in a format that supports transparency.
The resolution of Tokens created for use in Foundry is between 300px and 420px square for a medium or large sized creature. 400x400(px) has become somewhat of an industry standard for token creation. When zooming in on a token, it is desirable to get a higher resolution detail than you obtain with the battle-map itself. Foundry allows zoom up to 3x, so a token which has a resolution of 3 times the grid size of the battle-map will still demonstrate visible quality.
Token File Naming Conventions
If providing multiple varieties of the same base token, file naming conventions should allow all tokens to begin with the same file prefix.
For example, use the names
guard-red.png, guard-blue.png, guard-green.png instead of
red-guard.png, blue-guard.png, green-guard.png so that Foundry wildcard token paths can easily use
Foundry VTT uses a firm assumption that token artwork is facing "south" in it's natural orientation. If you have Tokens which are not southward-facing in the original images it is recommended to rotate the token images to have the tokens face south. Alternatively your users can utilize the mirror vertical checkbox in the token configuration to flip a northward facing token to be southward facing.
Avoid creating tokens which are facing diagonally, as there is no way in the Foundry application to correct for this initial orientation. For example, tokens which are drawn to face South-East or South-West as this will look unintuitive when those tokens are combined with rotation in Foundry VTT.
Foundry is extremely friendly to map creators wishing to package their content for distribution. The following are important guidelines to consider when creating maps for use in Foundry VTT.
1. Carefully align the grid for your map.
- Foundry assumes the grid starts from the top-left corner of the image.
- The grid should be fully flush with the edges of the image itself with no excess padding.
- The map should depict a whole number of grid spaces with no partial squares.
2. Exclude the visible grid from your final map image. While it is important that your map image be aligned with a grid, it is also preferable to not include that pre-rendered grid in the image itself. This allows users to better customize the map within Foundry by appling a different grid type, using it for gridless play, changing the grid color, or making other adjustments which the VTT can provide.
Video and Animation Assets
Foundry VTT supports three key filetypes when it comes to video assets for use. For transparent video assets, such as animated tiles or tokens, .webm will generally provide the best experience as it is high quality with a small file size. For animated assets (maps, tiles, and backgrounds) .webm, .mp4, and .m4v are supported
Decisions on video quality are a little more controversial than sizing for images. Foundry does not restrict the file size a Scene can use, but it is important to keep in mind that a scene must be distributed to all connected players and, potentially, the GM as well.
As a guideline, Foundry loosely recommends trying to keep video map file sizes in the vicinity of 50mb or less, to allow for adequate distribution. However, larger filesizes can be mitigated by users of Foundry through use of integrated support for S3, use of the preload feature, or if host and clients all have sufficient data transfer rates.
Video files should ideally be rendered at approximately 30fps or less. If your video includes audio, you can reduce impact on filesize by shipping the audio as a separate file to be triggered by Foundry's audio framework.
Lastly, you should strongly consider rendering map files as webm, using non-transparent for map scenes and transparent for tokens. The filesize differences between mp4, m4v, and webm provide a significant gain without quality reduction.
Video Codec and Bitrate
Foundry recommends codecs and bitrates optimized for online streaming. Variable Bit Rate (VBR) files rendered in h264 are usually the most performant while keeping quality high. If you are going to render the video in constrained or constant bitrate instead, consider a dual pass from a codec like libx264 at 2-5Mb/s. Quality percentage should be kept at 60-80% to reduce visual artefacting.
Particularly for streaming audio, file bitrate will generally be the most important factor in determining the smoothness and quality of an audio file played in Foundry.
A high bitrate provides higher-quality samples, but will be a bigger file that may not stream as quickly as the file is intended to play, and a low bitrate sample will be easier to stream over an internet connection, but may sound noticeably compressed, or have an overall lower quality. Overall, 128kbps is the minimum audio quality recommended for use in Foundry, with 192kbps being the suggested maximum. 128kbps provides the most optimal tradeoff between audio quality and smaller file sizes. Using higher bitrate samples than 192kbps will not provide a noticeable change in quality to most players.
This section does not cover the various codecs used in the creation/compression of sound files - however, they too are an important factor when it comes to exporting audio. Some codecs are better at exporting particular sounds, voices, or even genres of music. Your choice of format and codec may also be limited by which tools or digital audio workstation (DAW) you are using.
Choice of audio format is also an important consideration. Foundry currently supports OGG, MP3, FLAC, WAV, and WEBM file formats for audio playback. Reverb, cymbals, other drum samples, and certain pads or crisp-sounding instruments often suffer the most from audio compression, so results may vary from sample to sample. The supported audio formats for Foundry are listed below, with the general advantages and disadvantages of using each.
It's important to note that converting a file from one "lossy" format (such as MP3 or OGG) to another will simply compress an already-compressed sound file and reduce sound quality. Additionally, converting a lossy file to an uncompressed WAV format will not revert the loss in audio quality! It is best to have a lossless source file (such as a WAV or FLAC track) which is then converted once to your desired format.
- Arguably the best format for audio for the purpose of streaming online. An average OGG file will have similar filesize to a 128kbps MP3 file, but with clearer quality. Additionally, OGG comes with the added bonus of being able to loop cleanly in audio players that support the perfect looping of audio. Many tools and DAWs can natively export to this format as well, making it easy to create OGG files. However, Safari does not natively support OGG files.
- A fairly "standard" format. Provides a fairly solid tradeoff between audio quality and filesize, but is not as efficient with its compression as OGG and will not loop cleanly. Just about any device capable of playing sound files will be able to play MP3s. MP3 encoders such as LAME sometimes have a higher risk of developing artifacts or quantization errors in converted files, but is overall a safe choice.
- A lossless audio format, with manageable file sizes. FLAC files loop cleanly, and do not experience the quality drop normally seen in compression. However, FLAC files tend to have a larger bitrate than standard mp3 files. FLACs can still be useful, particularly for samples that more easily suffer a drop in quality when compressed, or on connections where bandwidth is not an issue (such as servers hosted over LAN).
- Solid, but lossy audio format designed for use on the web. WEBM codecs like Vorbis feature lossy compression like MP3, but the files tend to be smaller and have less of a loss in quality. Some browsers, like Safari, do not natively support WEBM, however, and encoding to a pure audio WEBM file is not available in most DAWs.
- WAV files are largely a poor choice for streaming online - uncompressed WAV files play the sound in its intended, perfectly-crisp quality, but can be an order of magnitude larger in size than compressed formats. This drawback alone almost always outweighs the nigh-unnoticeable difference in playback quality for most listeners.
Audio programs (such as Audacity) are available freely online that allow for exporting audio in various formats, under various codecs. The aforementioned program Audacity supports exporting to WAV, and OGG, with free plugins online to add support for exporting to MP3, FLAC, and other file formats.