SFTP for Beginners: Upload Mods Without Breaking Stuff

The good news is SFTP is basically the safest, least dramatic way to move mod files onto a game server. It’s not fancy. It’s not complicated. It just works. And if you follow a simple routine, you can upload mods, configs, maps, whatever, without bricking your server or triggering a rollback situation.

This guide is for total beginners. I’m going to assume you’ve never touched SFTP before, or you tried it once, got hit with a folder full of scary stuff, and backed out slowly.

By the end, you’ll know how to connect, what to upload, where to put it, and how to avoid the classic mistakes that break modded servers.

First, what is SFTP (and why you should care)?

SFTP stands for SSH File Transfer Protocol. In normal person terms, it’s a secure way to access your server files and upload and download stuff.

It’s like FTP, but not sketchy. It encrypts the connection. It’s less likely to randomly fail. And most hosting panels support it because it’s the standard.

If you’re hosting a Minecraft server, a Terraria server, a FiveM server, any of that, you will eventually need file access. Mods don’t magically install themselves. Same with plugin configs, resource packs, custom scripts, server icons, world files.

If you’re using a free hosting platform like Gaming4Free (gaming4free.net), SFTP is usually the cleanest way to manage your files without relying on slow web uploaders or weird zipped import tools.

What you need before you start

Keep this short. You only need a few things.

An SFTP client

Choose one of the following depending on your operating system:

• FileZilla — available on Windows, Mac, and Linux. The most widely used option.
• WinSCP — Windows only. Arguably simpler for beginners.
• Cyberduck — popular on Mac.

Your SFTP login details

You will need the following credentials, which you can find in your hosting panel. If you are on Gaming4Free, look in your server settings or the "SFTP details" area.

• Host (IP address or hostname)
• Port (often 22, sometimes custom)
• Username
• Password

A basic idea of what you are uploading

Know what type of file you are adding before you connect. Different games use different folder structures, but the rule of not overwriting core files applies everywhere.

• Mods (Forge or Fabric)
• Plugins (Spigot or Paper)
• Config files
• A world save
• FiveM resources and scripts

Pick a client: FileZilla or WinSCP

If you want the simplest experience

Use WinSCP. It feels like a normal file manager. Left side is your PC, right side is the server. Drag and drop. Done.

If you want the most common tutorial path

Use FileZilla. More people use it, so more screenshots exist online. It's also perfectly fine.

I'll explain the process in a way that works for either. The buttons move around, but the logic is the same.

Step 1: Connect to your server via SFTP

Open your SFTP client and create a new connection.

You will enter:

• Protocol: SFTP
• Host: (example: sftp.yourhost.com or an IP)
• Port: 22 (unless your panel says otherwise)
• Username: provided by the host
• Password: provided by the host

Then connect.

The first time warning (don’t panic)

You might see something like:

• “Unknown host key”
• “Trust this server?”
• A fingerprint string

This is normal. It’s basically your client saying, “Hey, I’ve never met this server, is it okay if we remember it?” If you’re sure you typed the correct host, you can accept and continue.

Now you should see two file trees:

• Your local machine files
• The server files

This is the moment where beginners usually go, “Uh, which folder do I click?”

So let’s talk about that.

Step 2: Understand the server folder layout (the part that saves you)

Every game server has a “root” folder, and inside it, the important stuff lives:

You’ll usually see things like:

• server.properties
• mods/
• plugins/
• world/
• config/
• logs/
• resources/
• .jar files (Minecraft server jar, or loaders)

Your job is to only touch what you intend to touch.

Not everything in there is yours to mess with. Some files are generated. Some are required for startup. Some are host-specific wrappers.

So here’s a rule that will save you:

If you don’t know what a file does, don’t delete it, and don’t overwrite it.

Download a copy first if you’re unsure. Which brings us to the safest workflow.

The safest mod upload workflow (copy this every time)

This is the routine I recommend if you don’t want surprises:

1. Stop the server
2. Download a backup of the folder you’re changing
3. Upload the mod/plugin/config
4. Double check file placement
5. Start the server
6. Check logs if something breaks

It sounds like extra work. It is extra work. It also prevents disasters.

Let’s go through each one quickly.

1) Stop the server

Do it from your hosting panel. Don’t just disconnect from SFTP and assume it’s fine.

Uploading files while the server is running can cause:

• Half written config files
• Corrupted worlds
• Mods not loading correctly
• Weird caching issues

Stop first. Always.

2) Backup the folder you’re changing

If you’re adding mods, backup:

• mods/
• config/

If you’re adding plugins, backup:

• plugins/

If you’re uploading a world, backup:

• the world folder, plus any world_nether and world_the_end style folders (Minecraft)
• the whole worlds/ directory (depending on server type)

In SFTP, backing up is as simple as dragging the folder from server to your PC. That’s it.

Do not skip this step if you care about the server.

3) Upload the mod/plugin/config

Drag and drop into the correct folder. Let it finish uploading fully.

If your client asks:

• “Overwrite?”
• “Resume?”
• “Keep newer file?”

Stop and think. Overwriting is where most breakages happen.

4) Double check file placement

This is boring, but it’s where you catch mistakes like:

• Uploading a mod zip instead of the .jar
• Putting mods in plugins/ (yes people do this)
• Having mods/mods/modfile.jar because you dragged the folder wrong

5) Start the server

Start it normally.

6) Check logs if it fails

If the server won’t start, don’t guess. Read the log. The log will usually tell you exactly what mod or file caused it.

Common “I broke my server” mistakes (and how to avoid them)

Mistake 1: Wrong mod loader version

Minecraft is the king of this problem.

Examples:

• You installed Forge mods on a Fabric server
• You installed Fabric mods on a Forge server
• Your mods are for 1.20.1 but your server is 1.20.4
• Your Forge version is wrong even though the MC version matches

How to avoid it:

• Match Minecraft version exactly
• Match loader type (Forge vs Fabric vs NeoForge)
• Match loader version if the mod requires it

If you’re on a hosting platform like Gaming4Free, double check what server software you selected when creating the server. It matters.

Mistake 2: Uploading client-only mods to a server

Some mods are meant for clients only. Minimap mods, shaders, UI mods, performance mods.

If you upload those to the server, it may crash on startup with errors like:

• “Class not found”
• “Client-side only”
• “Environment CLIENT”

How to avoid it:

• Read the mod page.
• If it says “client only”, don’t upload it to the server.
• If it says “server only” or “server + client”, you’re fine.

Mistake 3: Overwriting config files without realizing

Some servers generate configs on first run. If you overwrite them with configs from a different version of the mod, you get crashes or weird behavior.

How to avoid it:

• After adding a new mod, start the server once to generate fresh configs.
• Then change only what you need.
• Backup before editing.

Mistake 4: Uploading compressed files and expecting the server to unzip them

Most game servers will not unzip your upload automatically.

If you upload:

• mods.zip
• pluginpack.rar
• resources.tar.gz

The server will just see a zip sitting there. It won’t load anything inside it.

How to avoid it:

• Extract on your PC first.
• Upload the actual files. For Minecraft mods, that’s typically .jar files.

Mistake 5: Editing live files with a bad text editor

Some Windows editors mess up line endings or encoding, especially with JSON, YAML, or CFG files.

How to avoid it:

• Use something decent like VS Code or Notepad++.
• Don’t use Word. Please don’t use Word.

Where do mods go? Quick folder cheat sheet

This is not universal for every game, but it covers the usual stuff people host.

Minecraft

• Forge/Fabric mods: mods/
• Configs: config/
• Plugins (Paper/Spigot): plugins/
• World: usually world/ (or a custom name set in server.properties)

Important detail:

• Mods and plugins are not the same thing. A Forge server does not run Paper plugins the same way, and vice versa.

Terraria (tModLoader)

Terraria servers vary depending on how they’re hosted. Some hosts manage mods through the panel, some allow direct file placement. If your setup uses tModLoader, you’re usually dealing with:

• mod files (often .tmod)
• world files
• player data (sometimes)

If you’re not sure, don’t freestyle it. Check the host docs or the server directory structure first. Terraria is a little less standardized than Minecraft hosting.

FiveM

FiveM typically uses:

• resources/ for scripts and resource folders
• server.cfg for ensuring resources and setting permissions

Classic mistake here is uploading a resource folder one level too deep, like:

• resources/myresource/myresource/__resource.lua (wrong) Instead of:
• resources/myresource/__resource.lua (right)

And yes, it happens constantly.

Uploading a mod pack (the “bigger than one file” situation)

A mod pack isn’t just “mods”. It’s often:

• mods/
• config/
• defaultconfigs/
• kubejs/
• scripts/
• sometimes extra stuff like datapacks

The safest way to do a mod pack upload is:

1. Stop server
2. Backup current server folder (at least the mod related folders)
3. Upload mod pack folders one by one
4. Do not overwrite server core files unless you know exactly why
5. Start server, watch logs

Also, make sure the server has enough RAM/CPU for the pack. Some packs will technically “install” fine and still crash because the server runs out of memory during startup. That’s not an SFTP problem. It just looks like one when you’re new.

How to verify you didn't break anything (without waiting for players to complain)

After you start the server, run through these checks:

1. Check the console output. Look for "Done" or "Server started" style messages.
2. Scan for red errors. One missing dependency mod can stop everything.
3. Join the server yourself. Test the basics: world loads, chunks generate, commands work, no instant kick.

If it fails, don't keep restarting repeatedly hoping it fixes itself. Download latest.log or check the panel log viewer. The error usually names the mod file causing it.

Quick recovery plan if the server won't start

This is what you do when things go wrong, and you want the fastest path back to a working server.

1. Stop the server.
2. Remove the last mod or mods you uploaded.
3. Start the server again.
4. If it starts, you know the issue is in that batch.
5. Add mods back one at a time until it breaks again.

Slow, yes. But it's reliable, and it's way better than deleting random things in a panic.

If you made backups, the nuclear option is easy: delete the broken folder, re-upload your backup copy, and start the server. You're back.

A small note about free hosting and doing this efficiently

On free hosting platforms, upload speed can be a little slower, and you may have some limits depending on load. So do yourself a favor:

• Upload in batches.
• Avoid re uploading huge folders when only one file changed.
• Keep your own local backup of your server’s modpack and configs.

If you’re running your server on Gaming4Free, this is especially helpful because it makes experimenting painless. That’s kind of the point. Try stuff, break stuff safely, roll it back, keep going. No monthly hosting bill looming over you while you learn.

If you haven’t set up a server yet and you’re just practicing modding basics, you can start one at https://gaming4free.net and treat it like a sandbox. That’s honestly the best way to get comfortable with SFTP.

Final checklist (use this before every upload)

Before you upload anything, run through this:

• Server stopped
• I know which folder the files belong in
• I backed up the folder I’m changing
• Mods match server version and loader
• I’m not uploading client-only mods to the server
• I’m not overwriting unknown files
• After upload, I start the server and check logs

That’s it. Do this consistently and you’ll be the person in your friend group who “somehow” never breaks the server. Not because you’re lucky. Because you’re doing boring, correct steps every time.

And boring is good here. Boring means your server boots.

FAQs (Frequently Asked Questions)

What is SFTP and why should I use it for uploading mods to my game server?

SFTP stands for SSH File Transfer Protocol. It is a secure, encrypted way to access your server files and upload or download content. Unlike traditional FTP, SFTP is less likely to fail and is supported by most hosting panels. Using SFTP ensures safe and reliable file transfers, making it the preferred method for managing mods, configs, maps, and other files on game servers like Minecraft, Terraria, or FiveM.

What do I need before starting to upload mods via SFTP?

Before you begin, you need three main things: 1) An SFTP client such as FileZilla (Windows/Mac/Linux), WinSCP (Windows), or Cyberduck (Mac). 2) Your SFTP login details including host (IP or hostname), port number (usually 22), username, and password—available in your hosting panel. 3) A clear understanding of the files you intend to upload (mods, plugins, config files, world saves) to avoid overwriting important server files.

How do I connect to my game server using an SFTP client?

Open your chosen SFTP client and create a new connection using these details: Protocol set to SFTP; Host as provided by your host (e.g., sftp.yourhost.com or IP address); Port number (typically 22 unless specified otherwise); Username and password from your hosting panel. Upon first connection, you may receive a security warning about an unknown host key—accept this if you're sure of the server's identity. Once connected, you'll see your local files on one side and server files on the other.

Which folders should I be careful with when uploading mods on my server?

Game servers have essential folders like 'mods/', 'plugins/', 'config/', 'world/', 'logs/', and core files such as '.jar' files. You should only modify folders relevant to what you're uploading—for example, place mods in the 'mods/' folder and plugins in 'plugins/'. Avoid deleting or overwriting unknown files as they may be critical for server operation. Always back up any folder before making changes.

What is the safest workflow for uploading mods without breaking my server?

Follow this routine every time: 1) Stop the server from your hosting panel before uploading; 2) Download a backup of the folder you plan to change (e.g., 'mods/', 'plugins/'); 3) Upload your mod/plugin/config files carefully; 4) Double-check that files are placed correctly; 5) Start the server again; 6) Monitor server logs for any errors or issues. This process minimizes risks like corrupted worlds or broken mods.

Why should I stop my game server before uploading mods via SFTP?

Stopping the server prevents problems such as half-written config files, corrupted world data, improperly loaded mods, and caching issues that can occur if files are changed while the server is running. Uploading mod files while the server is active can lead to crashes or rollbacks. Always stop the server first through your hosting panel to ensure a smooth and safe file update.

Frequently Asked Questions