How to Match FreeBSD’s YouTube Seeking Speed on macOS
On FreeBSD, YouTube seeking can feel almost instant: click anywhere on the timeline and playback resumes immediately. On macOS, Firefox may pause briefly after seeking.
The safest way to approach this is to tune Firefox itself while leaving macOS networking unchanged. This keeps YouTube responsive without changing TCP behavior for Mail, video calls, VPNs, or other applications.
This guide uses conservative settings. It keeps HTTP/3, modern media formats, and hardware video decoding available, while avoiding excessive connection counts, forced codecs, aggressive buffering, and global macOS network changes.
1. Find your Firefox profile
Open Firefox and go to:
about:profiles
Find the profile you use and copy its Root Directory path.
For example:
/Users/your-user/Library/Application Support/Firefox/Profiles/your-profile
Replace the example path in the commands below with your own profile path.
2. Back up your Firefox settings
Quit Firefox completely before editing the profile:
osascript -e 'quit app "Firefox"' 2>/dev/null || true
sleep 2
Create a backup:
PROFILE="/Users/your-user/Library/Application Support/Firefox/Profiles/your-profile"
BACKUP="$HOME/Desktop/firefox-youtube-backup-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BACKUP"
cp -p "$PROFILE/user.js" "$BACKUP/user.js.before" 2>/dev/null || true
cp -p "$PROFILE/prefs.js" "$BACKUP/prefs.js.before" 2>/dev/null || true
echo "Backup saved to: $BACKUP"
No macOS TCP or sysctl settings are required for this configuration.
3. Apply the Firefox settings
If you already use user.js for other preferences, merge these lines into the existing file rather than replacing it.
// Conservative YouTube settings for macOS Firefox.
// Firefox-only: no global macOS TCP/sysctl tuning.
user_pref("network.http.http3.enable", true);
user_pref("network.http.altsvc.enabled", true);
user_pref("network.dns.disableIPv6", false);
user_pref("browser.cache.disk.enable", true);
user_pref("browser.cache.memory.enable", true);
user_pref("media.mediasource.enabled", true);
user_pref("media.mediasource.mp4.enabled", true);
user_pref("media.mp4.enabled", true);
user_pref("media.av1.enabled", true);
user_pref("media.mediasource.webm.enabled", true);
user_pref("media.mediasource.webm.audio.enabled", true);
user_pref("media.webm.enabled", true);
user_pref("media.hardware-video-decoding.enabled", true);
Most of these are Firefox defaults. Keeping them explicit makes the intended configuration easy to inspect and restore.
The configuration deliberately does not:
- increase Firefox’s global connection limits;
- disable HTTP request pacing;
- disable media throttling;
- force Firefox to use only H.264;
- disable AV1 or WebM support;
- force GPU acceleration;
- disable macOS App Nap;
- change global macOS TCP settings.
These options can increase memory use, create network bursts, reduce compatibility, or affect other applications.
4. Test YouTube
Start Firefox, open the same YouTube video, and seek repeatedly along the timeline.
For diagnostics, right-click the video and open Stats for nerds. Check:
- the selected codec;
- buffer health;
- dropped frames;
- whether seeking resumes quickly;
- whether other applications remain responsive.
The goal is not to force a particular codec. YouTube and Firefox should be free to choose the most suitable format for the hardware and network conditions.
5. Optional cache cleanup
If Firefox behaves inconsistently after changing preferences, clear its cache from:
Settings → Privacy & Security → Cookies and Site Data → Clear Data
There is normally no need to move profile directories manually.
Rollback
Quit Firefox and restore the backup created in step 2:
PROFILE="/Users/your-user/Library/Application Support/Firefox/Profiles/your-profile"
BACKUP="$HOME/Desktop/firefox-youtube-backup-YYYYMMDD-HHMMSS"
cp -p "$BACKUP/user.js.before" "$PROFILE/user.js" 2>/dev/null || rm -f "$PROFILE/user.js"
Then start Firefox again.
Conclusion
FreeBSD can feel faster during YouTube seeking because its desktop and browser environment may handle buffering and rendering differently. On macOS, the safest equivalent is a small Firefox-only configuration: keep HTTP/3 enabled, preserve modern codecs, use hardware video decoding when available, and avoid aggressive global network tuning.
This keeps YouTube seeking responsive without changing macOS networking or increasing the risk of interruptions during meetings and other network-heavy activities.