Why does StreamStash say 'Unable to extract user ID' on a TikTok feed?

This error usually means StreamStash cannot read a usable TikTok cookie. Open the Troubleshooting guide's TikTok section: confirm Firefox is set as the cookie source, that you are logged into TikTok in Firefox, and that the account has visited the creator's profile recently. If you use Chrome or Edge for cookies, fully close every window of that browser before launching StreamStash because the browser's exclusive cookie-database lock blocks the read.

Chrome is logged in but StreamStash reports no cookies — why?

Chrome, Edge, and Brave hold an exclusive Windows DPAPI lock on their cookie database while they are running, so StreamStash cannot read them. Fully close all windows of the browser (check the system tray, since Chrome often keeps a background process), then launch StreamStash. The cleanest long-term workflow is to use Firefox for the accounts you archive from — its cookie database is a plain SQLite file that StreamStash can read in milliseconds even with Firefox open.

Why does Instagram archiving feel slower or more conservative than other platforms?

Instagram has the strictest anti-automation system among the supported platforms. StreamStash uses a smart-schedule cadence (Active, Dormant, Quiet, Dead, Trial) per Instagram creator to stay inside Instagram's rate budget and avoid account challenges. The result is intentionally conservative polling. For high-volume Instagram workloads, a dedicated archival account is recommended.

Can StreamStash archive private or restricted accounts?

Only if the cookie session you authorise StreamStash with already has access. StreamStash uses your existing browser session, so it can see exactly what you can see when logged in to that account. It does not bypass platform privacy controls.

Where can I get help if I am still stuck?

Join the StreamStash Discord linked in the site nav for direct support, or email support@streamstash.live with your StreamStash version, the platform you are troubleshooting, and a description of the error. Most issues are resolved by checking cookie source, browser-lock state, or a temporary platform-side rate limit.

Troubleshooting

Troubleshooting Guide

Fix the setup issues that most often come from browser cookies, platform limits, and local storage expectations.

Use Firefox For Cookies

Firefox is the easiest browser to use with StreamStash. It stores cookies as a plain SQLite file that StreamStash can read quickly, while Chrome, Edge, and Brave encrypt their cookie database and often keep it locked while the browser is running.

Recommended setup: Open Firefox, visit the platform you want to archive from, sign in if needed, then launch StreamStash and refresh the feed or monitor.

Fix TikTok "Unable To Extract User ID"

This usually means TikTok returned a stripped-down response because the request had no usable cookies. StreamStash needs TikTok's profile metadata to enumerate a creator's videos, and TikTok may hide that metadata from cookieless requests.

Open Firefox and visit tiktok.com.
Sign in if the creator is restricted, private, regional, age-gated, or in a stricter moderation cohort.
Close and reopen StreamStash, then refresh the TikTok feed or monitor.
Try the creator profile URL again after Firefox has a fresh TikTok session.

If the profile still fails, try opening the same creator in Firefox directly. If TikTok itself shows a login wall, region block, or unavailable profile, StreamStash will see the same restriction.

Chrome Is Logged In But StreamStash Sees No Cookies

Chrome, Edge, and Brave can keep an exclusive lock on their cookie database even after the visible browser window is closed. Background processes can keep running, and Windows DPAPI encryption can also prevent cookie reads from working reliably.

You can either switch to Firefox, or fully close every chrome.exe, msedge.exe, or brave.exe process in Task Manager before launching StreamStash.

Private And Restricted Content

StreamStash can access content your own authenticated browser session can access. That includes Instagram private profiles you follow, Telegram restricted or private channels when configured with your own credentials, and age-restricted TikTok content visible to your account.

Use your own access: StreamStash does not bypass platform permissions. If your browser account cannot view something, StreamStash cannot archive it.

Why Instagram Downloads Run Differently

Instagram downloads run as a full profile cycle rather than one isolated post at a time. StreamStash checks the profile, downloads new eligible content in one pass, then waits for the next scheduled check.

This is intentional. It reduces repeated profile hits, works better with Instagram's session behavior, and keeps rate-limit pressure lower.

Source Quality Instead Of Upscaling

StreamStash downloads source-quality media where the platform makes it available. Earlier AI upscaling experiments did not add meaningful detail, because upscalers cannot recover information that was never present in the compressed stream.

For archival work, the original platform file is the version worth preserving. It avoids artificial sharpening, larger files, and wasted GPU time.

No NAS Or Cloud Required

The public StreamStash build runs as a Windows desktop app. You do not need a NAS, server, Docker container, Python install, or cloud database to use it.

There is no hosted cloud version. StreamStash stores your archive on your hardware, with local app data and a local database. Docker, NAS, macOS, and Linux builds are planned separately.

Still Stuck?

The fastest support route is the Discord community. For private issues like refunds, license keys, or account-specific troubleshooting, email support@streamstash.live.