Decker's web exports are self-contained monolithic .html files, with no required "server-side" component; they can be served statically as part of any web page. Web-Decker strictly executes on the viewer's web browser. It is possible for scripts to prompt users to select and open files from their local filesystem, but there is no mechanism for referencing or fetching external files automatically, irrespective of where the deck is stored. In general, if a deck needs data, the data should be embedded in the deck.