Elementum Settings on Firestick: Memory vs Disk Mode Tested

You installed Elementum. It opened. Then the first stream stalled at 34%, and the second one threw a “not enough space” warning. The addon isn’t broken. The default elementum settings firestick owners start with were written with desktop machines in mind, with big drives and RAM to spare. I spent several weeks into 2026 running head-to-head tests on Fire TV hardware, and a handful of changes fixed most of the stuttering I saw.

This isn’t an install guide. It assumes Elementum already runs and you just want it to run well. We’ll cover memory mode vs disk mode, buffer values per device, moving downloads to a USB drive, and how much a VPN costs you in speed. There are three copy-paste profiles at the end.

Why Elementum’s Default Settings Struggle on a Firestick

Quick refresher. Elementum is a torrent-streaming addon for Kodi. It runs a small background program, called a daemon, that grabs pieces of a file in sequence and hands them to Kodi’s player. The official Elementum GitHub repository ships defaults that assume a PC with a large drive and spare memory. A stick that sells for around $30 on sale has neither.

If you still need the setup steps or want my safety findings first, read my Elementum MRSP torrent streaming risk test before changing anything here.

8GB Storage and 1-2GB RAM: The Real Bottleneck

The numbers are grim. The Fire TV Stick Lite (2020) has 1GB of RAM and 8GB of storage. The first-gen Fire TV Stick 4K from 2018 bumps RAM to 1.5GB but keeps the same 8GB. Fire OS and Amazon’s preinstalled apps eat a big chunk of that, so my Lite showed about 4.6GB free on a fresh setup.

Then Kodi moves in with its own database, thumbnail cache and addons. By the time I’d added Elementum and a couple of other addons, the Lite was down to roughly 3.1GB. One 1080p movie can easily run 4GB or more. You can see the problem.

RAM is just as tight. With Kodi in the foreground and Elementum’s daemon running behind it, the Lite had only a few hundred megabytes left over for buffering.

What Happens When the Cache Fills Mid-Stream

Disk mode writes the entire file to the download folder as it plays. On the Lite, a 4.2GB public-domain film filled internal storage somewhere around the 70-minute mark. Playback froze. Kodi popped a storage warning, and the stream never came back.

The Stick 4K failed more quietly, which I actually think is worse. It didn’t crash. Fire OS started clearing app caches in the background to claw back space, and playback stuttered every few minutes while the system fought over storage. Have you seen random stalls that vanish after a reboot? A full disk is the most likely culprit.

A Quick Note on Legal Use Before Tuning Anything

Torrent streaming works differently from regular streaming. While Elementum downloads, it also uploads pieces to other peers, and every one of those peers can see your IP address. That holds for every mode and every setting in this guide. No exceptions.

Only use Elementum with material you have the right to share, like public-domain films and Creative Commons releases. Every file I tested came from public-domain torrents on the Internet Archive or from the Blender Foundation’s Creative Commons open movies.

Memory Mode vs Disk (Storage) Mode: Head-to-Head Test

This is the big decision. Memory mode keeps a sliding window of the file in RAM and throws away pieces you’ve already watched. Disk mode, labeled “File” in some versions, saves the whole thing to storage. Here’s how elementum memory mode vs storage mode played out on real Fire TV hardware.

Test Setup: Devices, Network and Sample Files

• Devices: Fire TV Stick Lite, Fire TV Stick 4K (1st gen), and Fire TV Cube (3rd gen)
• Software: Kodi 21.2 Omega with the latest Elementum release from the official repository at the time of testing
• Network: 300Mbps fiber, 5GHz Wi-Fi, with the router about 4 meters from the TV
• Files: Night of the Living Dead (1968, public domain, 1.4GB), Sintel (CC-BY, 1080p, 1.1GB), and Tears of Steel (CC-BY, 4K, 6.3GB)
• Runs: I played each file three times per mode per device, rebooting and clearing the cache between runs.

Swarm health swings wildly from hour to hour, so read these as relative numbers. Your absolute times will differ, maybe by a lot.

Time-to-First-Frame Results

*Most of the Lite’s disk-mode stalls happened as storage ran low, not because of network problems.

Memory mode started faster on all three devices. No surprise there. Writing to cheap eMMC flash adds a small delay before the buffer is ready, and RAM doesn’t have that overhead.

Mid-Stream Stalls and Seek Behavior

Seeking is where the two modes really part ways. In memory mode, jumping 40 minutes ahead in the 6.3GB Tears of Steel file forced Elementum to fetch a fresh batch of pieces, which took 30 to 50 seconds on the Lite. Going backward was just as slow, because those already-watched pieces were gone.

Disk mode keeps everything. Rewinding was instant. Jumping forward only meant waiting on pieces that hadn’t arrived yet. If you skip around a lot or rewatch scenes (I do this constantly with anything that has a good fight sequence), disk mode with enough space wins clearly.

Effect on Free Storage and Device Heat

Memory mode didn’t touch storage on any device. That alone makes it the safe default for anyone with an 8GB stick and no USB drive.

Heat was a smaller surprise. After 90 minutes of disk-mode playback, the back of my Stick 4K felt noticeably warmer than it did in memory mode, which I put down to constant flash writes. I didn’t catch any thermal throttling. The Lite, though, felt sluggish in menus after long disk-mode sessions until I rebooted it. Constant writes also wear flash memory over time, so I wouldn’t run disk mode on internal storage every single day.

The Elementum Settings Firestick Users Should Actually Change

Open Kodi and go to Add-ons → My add-ons → Video add-ons → Elementum → Configure. Tab names have shifted a bit between releases, so if a setting isn’t where I say it is, check the neighboring tabs. Below are the settings that made a measurable difference, plus a few that didn’t.

Memory Size / Buffer Size Values by Device

People mix these two up all the time. Memory size is how much RAM memory mode can use for the whole download window. Buffer size is how much data Elementum collects before playback starts. Getting the elementum buffer size right in Kodi means trading startup time against stalls.

I got greedy on the Lite once and pushed memory size to 300MB. Kodi crashed back to the Fire TV home screen twice in 20 minutes. Fire OS kills apps aggressively when RAM runs low, and Kodi is almost always first in line.

Recent builds include an auto memory size option. On the Cube it chose sensible values. On the Lite it picked a number high enough to cause those same crashes, so I switched it off and set the value by hand. (It’s off by default in some builds and on in others, so check yours.)

Download and Upload Rate Limits

Leave the download limit at 0, which means unlimited, unless someone else in the house starts complaining about lag. A 1080p stream needs only about 1 to 2MB/s. The extra headroom builds a safety margin that absorbs dips in the swarm.

Upload is trickier. At an extremely low cap like 10KB/s, other peers became less willing to share with me, and startup times climbed by about 30%. That’s how BitTorrent’s tit-for-tat logic works: stingy uploaders get deprioritized. A cap of 100 to 200KB/s kept things fair without choking my home upload. On the Lite, it also trimmed CPU load slightly.

Max Connections and Peer Limits

I didn’t expect much from this one. I was wrong. On the Lite, dropping the connection limit to 100 cut menu lag during playback and removed about one stall per hour on average. The Cube and Stick 4K handled 200 without breaking a sweat.

Going above 200 didn’t speed anything up on any device. Healthy swarms filled the buffer long before that ceiling mattered.

Auto-Clear Files After Playback

In disk mode, set the “keep files” options to delete files after playback stops and after downloads finish. “Ask” sounds safer. It isn’t. If you dismiss the prompt with the remote, the files stay on disk, and that’s exactly how a Firestick quietly runs out of space over a week.

For most people, this single setting fixes elementum low storage firestick complaints. Memory mode users can skip it, since nothing gets written to disk anyway.

Settings that made no measurable difference in my tests: encryption policy, user-agent spoofing, and toggling UPnP/NAT-PMP while connected through a VPN. Leave them at their defaults.

Using a USB Drive as Elementum’s Download Path

Want disk mode’s better seeking without filling up an 8GB stick? Use external storage. Changing the elementum download path to USB was the single most useful upgrade I made to my Stick 4K.

OTG Adapter and Drive Format Requirements

The Fire TV Stick Lite, Stick 4K and 4K Max have just one micro-USB port, and it’s used for power. You’ll need a powered OTG adapter, which splits that port so you can connect power and a USB drive at once. Expect to pay around $8 to $12 on Amazon. The 3rd-gen Fire TV Cube makes this easier, because it has a full-size USB-A port and you can plug a drive straight in. Older Cubes need an OTG cable.

Format the drive on a computer first, as FAT32 or exFAT. FAT32 can’t hold files over 4GB, which rules out most 4K files, so pick exFAT. When Fire OS asks, set the drive up as removable/portable storage rather than internal storage. That keeps things simple and lets you unplug it later without drama.

Pointing Elementum to External Storage

1. Plug in the drive and wait for Fire OS to detect it. A notification usually appears.
2. Open Kodi, go to Elementum → Configure, and find Download path.
3. Browse to the USB drive. It’ll show up with a name like /storage/1A2B-3C4D/.
4. Go to Android/data/org.xbmc.kodi/files/ on that drive and create an “elementum” folder there.
5. Select that folder, set the storage type to File, and restart Kodi.

Step 4 is the one people skip. Android restricts where apps can write on removable drives. Kodi can read the whole USB drive, but it can only write inside its own app folder. Point Elementum at the root of the drive and you’ll get the dreaded “path not writable” error. The Kodi wiki’s Android section describes the same restriction.

No Android/data folder on the drive yet? Open Kodi’s file manager once with the drive connected. Fire OS usually creates it automatically after that (it took two tries on my Stick 4K, for what it’s worth).

Speed Penalty: USB 2.0 vs Internal Flash

The Firestick’s port runs at USB 2.0 speeds, whatever drive you plug in. I measured roughly 18 to 22MB/s of sustained writes to a SanDisk USB 3.0 drive. That’s still far more than the 1 to 2MB/s a 1080p stream needs, and comfortably more than 4K needs too.

Startup ran about 2 seconds slower than on internal flash. In return, I got over 100GB of space and no more storage warnings. Easy trade.

How a VPN Changes Elementum Performance

Memory mode doesn’t hide you. Peers see your IP whether pieces sit in RAM or on disk, because the exposure comes from the peer connection itself. Elementum’s traffic needs to stay inside the VPN tunnel, and the protocol you pick affects how fast it runs.

Protocol Choice for Peer Connections

Encryption takes CPU. The Lite’s quad-core chip is weak, and it shows. Here are the average Elementum download rates I saw on Sintel:

WireGuard won easily. OpenVPN on the Lite still kept up with 1080p, but startup dragged noticeably. For a deeper look at protocols, see my VPN protocol speed tests on Firestick.

Port forwarding is the other factor. Without a forwarded port, other peers can’t open connections to you, which shrinks the pool you can pull from. Only a few providers still support port forwarding on P2P servers as of late 2025, and setting it up on Fire TV can be fiddly. Weak swarms benefit the most from it. I haven’t tested enough providers to recommend a specific one.

Split Tunneling: Should Elementum Go Through the VPN?

Yes, keep it inside the tunnel. Here’s the catch: Fire TV VPN apps split traffic per app, and Elementum’s daemon runs under the Kodi app. You can’t route Elementum through the VPN while letting the rest of Kodi bypass it. Put all of Kodi in the tunnel.

If another app misbehaves with the VPN on, like a banking or local TV app, exclude that app instead. My Kodi VPN split tunneling guide explains what to route and what tends to break.

Troubleshooting Elementum Stuttering After Tuning

Still stalling after all that? It’s usually one of three things. Here’s a quick elementum stuttering fix list, matching each symptom to the most likely settings problem.

Stuck at ‘Waiting for Metadata’

• Cause: Elementum can’t find peers to get the torrent’s file list from.
• Check: Make sure DHT is enabled. A disabled DHT caused this twice during my testing.
• Check: If your VPN app has a “block LAN/local traffic” or strict kill switch option, it may be blocking the daemon. Reconnect the VPN, then restart Kodi.
• Check: The swarm might just be dead. Try a well-seeded public-domain file to confirm your setup works.

Buffering Loop at 99%

• Cause: The buffer is bigger than memory size allows, so it never finishes filling.
• Fix: Keep buffer size well under memory size. A buffer of about 15–20% of memory size worked reliably for me.
• Disk mode: Check free space at Settings → My Fire TV → About → Storage. Below roughly 500MB free, Elementum can stall right before playback starts.

Elementum Daemon Crashes or Won’t Start

• Fix 1: Clear Elementum’s cache and leftover files. Deleting old partial downloads from the download path stopped two crashes on my Lite.
• Fix 2: Restart the daemon. Force-stop Kodi from Settings → Applications → Manage Installed Applications → Kodi, then reopen it.
• Fix 3: Lower memory size. On 1GB devices, daemon crashes are usually Fire OS killing it for hogging RAM.
• Fix 4: If the download path points to a USB drive that’s been unplugged, Elementum may fail silently at startup. Reconnect the drive or reset the path to internal storage.

Bodhi’s Recommended Elementum Profiles

These are the exact values I run at home. Copy the profile that fits your hardware, then tweak one setting at a time. Change three things at once and you’ll never know which one helped.

Profile 1: Fire TV Stick Lite (Memory Mode)

• Storage type: Memory
• Auto memory size: Off
• Memory size: 150MB
• Buffer size: 20MB
• Max download rate: 0 (unlimited)
• Max upload rate: 100KB/s
• Connections limit: 100
• VPN protocol: WireGuard

Profile 2: Fire TV Stick 4K with USB (Disk Mode)

• Storage type: File
• Download path: /storage/XXXX-XXXX/Android/data/org.xbmc.kodi/files/elementum/
• Buffer size: 30–40MB
• Max download rate: 0 (unlimited)
• Max upload rate: 200KB/s
• Connections limit: 200
• Keep files after playback / after finished: Delete
• Drive format: exFAT

Profile 3: Fire TV Cube or NVIDIA Shield (Balanced)

• Storage type: Memory for casual viewing, File on internal storage if you seek a lot
• Memory size: 400MB (the Shield TV Pro has 3GB of RAM, so it can handle more)
• Buffer size: 50MB
• Max upload rate: 200–300KB/s
• Connections limit: 200
• Keep files: Delete

Verdict: For most people, the best elementum settings firestick setup is memory mode with a memory size matched to your RAM. It’s stable, and it physically can’t fill your storage. Switch to disk mode only once you have a correctly configured USB drive or a device with real storage to spare. Either way, keep Kodi inside a WireGuard tunnel. And please don’t run disk mode on 8GB of internal storage without auto-delete turned on.

⚖️ Legal Disclaimer: IPTV Wire does not own or operate any streaming service, application, or website mentioned in this article. We do not verify whether third-party services carry proper licensing. Users are responsible for ensuring they comply with copyright laws in their jurisdiction.

Frequently Asked Questions

Should I use memory mode or storage mode in Elementum on a Firestick?

Use memory mode on 8GB Firesticks unless you’ve connected a USB drive. It never touches your storage and starts slightly faster. Storage (disk) mode handles seeking better, but it needs several gigabytes free for each title.

What buffer size should I set in Elementum for smooth playback?

Start at 20MB on a Stick Lite, 30–40MB on a Stick 4K or 4K Max, and about 50MB on a Cube. Keep the buffer at roughly 15–20% of your memory size. Go higher and playback can get stuck at 99%.

Why does Elementum fill up my Firestick storage?

In disk mode, Elementum saves the whole file, and the default options can leave those files behind after you stop watching. Set the “keep files” options to Delete, or switch to memory mode.

Can Elementum save files to a USB drive on Fire TV?

Yes. Connect an exFAT-formatted drive through a powered OTG adapter, or plug it straight into the USB-A port on a 3rd-gen Cube. Then set the download path to Kodi’s app folder on the drive: Android/data/org.xbmc.kodi/files/. Any other folder triggers a “path not writable” error.

Does Elementum need a VPN even if it streams in memory mode?

Yes. Memory mode only changes where pieces are stored. You still connect and upload to peers, so your IP is visible either way. Run Kodi through the VPN, ideally on WireGuard.

Why is Elementum stuck on ‘waiting for metadata’?

Elementum can’t reach any peers to pull the torrent’s details. Make sure DHT is on, reconnect your VPN, and restart Kodi. Then test with a well-seeded public-domain file to rule out a dead swarm.