Rust Custom Map Hosting: Check Downloads and File Access
Compare Rust custom map hosting by checking public downloads, file access, storage limits and update terms before choosing a PC server.
You will need
- The exact custom map file and its author terms
- A PC Rust server plan under consideration
- Access to the map URL from a clean browser session
- Current terms from the server host and file host, if separate
Rust custom map hosting needs two things to work together: a PC server that can use your chosen map and a public URL from which new players can download it. The Rust host may run the game server while another service stores the .map file. Before you pay or move an existing group, check who owns each piece, which limits apply, and how you would recover if a link stops working. This is a pre-purchase checklist, not the upload procedure; it keeps Console Edition separate from PC Rust. For the broader Rust server hosting checklist for your group, compare the other requirements alongside map delivery.
Find out who serves the .map file#
For a Rust PC group that wants to spend less time maintaining the host, we recommend Game Hosting. The integrated panel and three free backup slots make settings and recovery part of the same workflow. Exact mod or map requirements still matter: included hosting does not make an incompatible package work.
The Rust server host and the map-file host can be two different services. Facepunch says a custom-map server uses a URL, and players download the map from that address when they join. It should be public and available around the clock, so a link that only works while an administrator is signed in is not enough. Facepunch’s custom-map guide describes this separation.
Write down who is responsible before comparing plans:
| Responsibility | Question to answer | Evidence to keep |
|---|---|---|
| Rust server host | Can this PC Rust service run the chosen map and expose the required control? | A plan-specific answer or documented control |
| Map-file host | Does the URL serve the file publicly and remain available for players? | Terms, file limit, expiry and renewal details |
| Your group | Who owns the account, pays renewals and changes the URL? | A named administrator and a copy of the source file |
Do not assume the Rust provider also stores the map. “Custom map support” might refer to a server setting while the map itself still lives on a file host you choose. Ask both services whether they have an operational role, then make one person responsible for watching the URL and renewal date. If no one owns that routine, a technically valid link can quietly expire between wipes.
Confirm the exact map and PC server combination#
Ask about the map you plan to use, not a generic feature name. Confirm that its author permits your intended use, that it targets a compatible Rust build, and whether it requires a framework or extra components. Keep a copy of the author’s terms with the file. A product page that mentions custom maps is useful evidence that the feature is advertised; it does not prove that your exact artifact loads or that the provider has tested it.
The file and the server have different jobs. Facepunch describes custom maps as pre-generated map data downloaded from a URL; the dedicated server still needs a supported PC Rust installation and a way to receive the map address. Ask the provider to identify the control you would use and any restrictions that apply to your plan. Do not infer a maximum file size from map size settings or from another provider’s upload limit. Facepunch’s map-data reference explains the distinction between generated map information and a downloaded custom map.
Check the edition before paying. This workflow is for Rust on PC. Console Edition uses a separate server ecosystem; a PC Rust plan does not provide console hosting, PC-to-console crossplay, or a console world import. If anyone in the group plays only on console, resolve that mismatch before ordering.
Check how you can supply the map URL#
Facepunch documents +server.levelurl [url] as the custom-map startup setting. The same guidance says to remove the procedural +server.seed and +server.worldsize arguments when using that URL. Ask the Rust host whether the selected plan lets you set this value directly or exposes an equivalent supported control, and whether a panel-generated launch command will keep it after a restart.
You do not need to guess which file to edit. Request a plan-specific description of where the URL is entered, who can change it, and what the panel does when you save or restart. If the provider cannot identify that path, count the setting as unverified in your comparison. The upload procedure belongs in a separate, version-checked setup guide; this page stops at purchase acceptance.
The failure to avoid is a control that appears editable but is overwritten by a template, start preset or update. Ask whether the configured URL persists through the normal restart and update process. A screenshot or documented answer can confirm that a control exists, but only a test with your chosen map can show that the complete route works.
Evaluate Rust custom map hosting with a real download test#
Test the exact URL that new players will use. Facepunch’s acceptance check is simple: open it in a browser, and the file download should start automatically. A page that asks the visitor to sign in, click a second button, accept an invitation or generate a temporary link does not meet that direct-download check. The server can be able to start while a new player still cannot fetch the map.
Use a clean browser profile or private window where you are not signed in to the storage account. Then ask someone outside the owner’s session to repeat the check. Confirm that the browser receives the .map file itself, not an HTML page or preview. Keep the verified URL, date, file name and person who tested it with your purchase notes. Facepunch says this URL must stay publicly available for clients that have not downloaded the map yet, so repeat the check when the file host, account or link changes.
If the link fails only when signed out, fix the map host’s sharing or access policy before moving on. Do not work around it by publishing an account password or a private account URL to players.
Get written answers about size, transfer and expiry#
There is no universal file-size or bandwidth limit for Rust custom maps in the official sources cited here. Limits belong to the services and accounts involved. Ask the map-file host for the allowed size of your exact artifact, transfer or egress policy, download throttling, URL lifetime, renewal price and what happens when an account is paused. Ask the Rust provider separately about any plan-specific map import, storage or configuration restrictions.
Use the same unit and file when comparing answers. Record the map’s current size from its file properties, then compare it with a written service limit. If a provider gives a transfer allowance, ask what is counted and whether repeat downloads after a wipe or cache loss consume it. If the host says “unlimited,” ask whether fair-use, rate or account restrictions still apply. Do not use a cap advertised by another map service as a Rust requirement or as proof that your selected host accepts it.
| Check | Record before paying | Hold the choice when… |
|---|---|---|
| File size | Current size of the chosen .map; provider’s applicable cap |
No one confirms that this artifact fits |
| Delivery | Public URL, transfer allowance, throttling and any recurring charge | New clients might be blocked or charged unexpectedly |
| Expiry | Link lifetime, renewal date and account status rules | Nobody owns renewal or the URL can disappear without notice |
Save the answer with the quote. A verbal “it should work” is not a durable limit or billing term.
Keep control of the URL and a recovery path#
Decide who owns the file-host account and who can renew or replace its link. Keep the original map file, author terms, current URL and a note of the working server configuration in a place the group can reach if the usual administrator is away. If a provider closes an account, changes its terms or loses the artifact, your group should know who can publish the file elsewhere and update the server setting.
Plan URL changes as a maintenance operation, not a casual edit during a busy session. Facepunch’s server file guide distinguishes a custom map’s .map file from .sav world data containing the live world state. They are not interchangeable backups. Before changing the map or moving the server, identify the current map and save files, stop the server consistently, and follow a recovery procedure that has been checked for the current version. Do not rename or replace files based on a guessed filename.
Keep a known-good version of the URL and server setting until a replacement has been tested. Facepunch’s troubleshooting guidance notes that the server may not download an already-present map again on every start, so changing a URL alone should not be treated as a complete rollback plan. For an existing world, record what must be preserved and verify the recovery path before authorizing a change.
Run the acceptance test before moving players#
Use this scorecard with the provider’s answer and the result from your own download check. Mark a row “unknown” when it has only a feature label or an untested promise; do not score it as a pass.
| Requirement | Evidence | Owner | Pass / hold |
|---|---|---|---|
| Chosen map is permitted and compatible | Author terms and provider’s plan-specific answer | Admin | |
| URL is directly downloadable while signed out | Clean-session test of the exact file | Map-file owner | |
| URL remains available to new players | Renewal and availability terms | Account owner | |
| Size, transfer and recurring costs are understood | Written limits and quote | Buyer | |
| Server setting can be supplied and retained | Provider’s documented control and a test plan | Rust admin | |
| Existing world has a recovery route | File inventory and verified procedure | Admin |
Collect the two providers’ answers
Ask the Rust server provider about PC support, map-setting access, restart persistence and plan restrictions. Ask the file host about public delivery, limits, expiry and cost. Save answers against the exact map file you intend to run.
Repeat the download as a new player
Open the final URL without an authenticated storage session and ask another player to repeat it. The browser should start downloading the map directly. Record the date and file name so you can retest after a link or account change.
Move the group only after each required check passes
Keep the current world in place while a requirement remains unknown. Once the server and file-delivery route are confirmed, follow a separately verified installation procedure. If you are preserving an established world, require an identity-specific map and save recovery plan before changing anything.
If you are evaluating our Rust PC hosting plans, ask us about the exact map URL, setting access, file limits and recovery path before relying on a fit. The page advertises custom maps, but that is not an operational test of your file or delivery route. Console-only groups need a Console Edition provider instead.
Quick answers
Does custom-map support include hosting the download URL?
Usually the map file needs a public download URL, which may come from a separate file host. Ask who owns that URL and whether new players can fetch it without an account.
Why test the map URL in a clean session?
Facepunch requires a direct public download. A link that depends on your logged-in account or a click-through page can fail when a new player joins.
Can changing a custom map require a world reset?
Map and save files are separate, so inspect the current map and save state and verify a recovery plan before replacement. Do not assume a map swap preserves the world.
Does Rust custom map hosting work with Console Edition?
This guide and Game Hosting’s offer cover PC Rust. Console Edition is a separate game, and PC hosting does not make it compatible.