DramaFork Work Export: How to Choose Between a Local Asset Package and a Remote Link Package, and How to Accept Them?
For offline display, long-term archiving, or recipients with unstable networks, prioritize checking the local asset package; if you want to reduce the transmitted file size, the recipient can connect to the internet, and the asset service remains continuously available, you can choose the remote link package. Both must be accepted on another device; downloading the ZIP only proves that file delivery is complete, not that the entire work is playable.
Introduction
For offline display, long-term archiving, or recipients with unstable networks, prioritize checking the local asset package; if you want to reduce the transmitted file size, the recipient can connect to the internet, and the asset service remains continuously available, you can choose the remote link package. Both must be accepted on another device; downloading the ZIP only proves that file delivery is complete, not that the entire work is playable.
This article was compiled by DramaFork based on the export implementation as of October 4, 2026. It provides mode descriptions and acceptance methods, and does not include measured results, download speeds, or compression ratios from formal deployment.
Where the two package types place assets
| Comparison item | Local asset package | Remote link package |
|---|---|---|
| Video source | Local assets written into the ZIP | Access the asset service over the network |
| Network conditions | Once the complete assets and player are ready, it can run offline according to the instructions in the package | Playback depends on the network and related services |
| File size | Includes media, usually larger | Does not write video files, usually smaller |
| Delivery focus | Confirm that assets are complete, and that extraction and startup work properly | Confirm that the address can be accessed from the recipient device |
| Long-term preservation | Keep the complete package and instructions | Also keep a complete asset backup and check service dependencies |
The remote package stores a stable asset interface address, and the service retrieves the corresponding asset when accessed. A stable entry point reduces the risk of hardcoding temporary links into the package, but it does not mean the service will always be available, nor does it mean all devices have passed acceptance.
The local package is better suited for independent safekeeping. However, the exported player and story data are not the same as a complete creation editor. Continued production should still retain the project and source assets; do not assume the ZIP can be directly imported back into other tools for continued editing.
Before exporting, first confirm that the current project can be fully playtested
Check the entry point, storyboard playback, the targets of all choices, and the ending pages. If a certain video is not yet complete, or a node reference is invalid, resolve project completeness first, then handle export.
Also check whether the project has been saved, and whether the assets used for export still correspond to the latest script. After just modifying dialogue, nodes, or characters, old previews and old packages may retain previous results; do not judge version correctness based only on file creation time.
You can record a delivery checklist: project version description, paths that need to be covered, expected endings, and current asset status. It is the basis for the recipient's acceptance and does not need to include internal prompts, account configuration, or service keys.
How to choose image quality for the local asset package
The current local export provides original quality, standard compression, and high compression. Original quality preserves the source video; standard compression has a resolution cap of 1080p, and high compression has a cap of 720p. The cap is not a fixed output resolution; the source assets and image content will still affect the result.
First choose the mode closest to the delivery task. If formal review focuses on image details, consider original quality; for ordinary sharing, you can first look at standard compression; under restricted devices or transmission conditions, then compare whether high compression retains the necessary information.
Do not promise a fixed reduction percentage. Small character movements, dark-area gradation, subtitles, and evidence details have different sensitivities to compression. Inspection should use the segment in the work that is hardest to see clearly, rather than only playing a bright opening.
Keep a backup of the original assets, then choose the delivery version. In this way, even if the low-size version is unsuitable, it can be remade, avoiding being left with only an already compressed copy.
Accept the export result in order
- Download the ZIP completely, then extract it to a separate directory. Do not treat successfully playing a single file in the compression software's preview window as the whole package passing.
- Run the player according to the instructions in the package, and use the provided startup method if necessary. Browsers and systems may handle local files differently.
- Walk through one path from the opening and record the choices and ending you pass through.
- Return to the entry point, walk through another affected path, and confirm that choices do not jump to old nodes.
- Check the cover, videos, and ending pages; when there is sound, check volume transitions, and when there is failure, confirm the prompt and retry entry point.
- Recheck on another target device, recording the system, browser, package version, and network conditions.
For the local package, you should also turn off the network and confirm that the required assets are not borrowing browser cache or cloud addresses. For the remote package, test on the real recipient device and network; do not just open it once on the production computer.
The remote package opens on my machine, so why can the recipient still not open it?
First check whether the asset entry point points to a formally accessible site. A local development address only represents the service on the production device; writing it into the remote package does not automatically let other computers connect to that device.
If the asset service domain has been changed, re-export and accept according to the actual deployment. Do not just modify the package's file name and continue sending content with the old address.
Second, distinguish between "the package is missing asset entries" and "there is an asset address but loading fails." The former requires going back to the project for inspection; the latter should verify the network, service, and asset availability. Although the remote package does not require players to enter a creation account, it still depends on the asset service running correctly.
A stable address solves the entry-point problem, but it cannot eliminate service downtime, asset deletion, or configuration errors. When future display needs to be independent of the service, prepare a local asset package.
When sending it to others, include four explanations
Tell the recipient the work version, startup method, whether the network is needed, and the path that should be experienced in this round. If you are only inviting review of the core choices, you can note that art completeness is not being evaluated for now, but you must not skip issues that already block playback.
Use an acceptance record to save "on which device, under which network conditions, which paths were completed." These results must be filled in after actual observation; do not write pending check items as passed in advance.
DramaFork provides a process from creation to web work export. Before delivery, do one final independent opening: let the recipient complete the playtest using only the package and instructions. Only then can you know whether the work can still be experienced correctly after leaving the production environment.
