Auto-start makes Free Tab Switcher start rotating your tabs as soon as Chrome opens. It's built for screens nobody touches: IT dashboards, digital signage and 24/7 monitoring.
This guide covers setup, what auto-start does and doesn't keep, and troubleshooting.
π― What is Autostart?
Autostart automatically activates Free Tab Switcher when Chrome launches, eliminating the need to manually enable cycling after each browser restart. This is essential for:
- Unattended monitoring systems
- Digital signage displays
- 24/7 dashboard monitoring
- Automated surveillance setups
- Kiosk applications
β‘ Quick Setup (5 Minutes)
Step 1: Turn On Auto-Start
- Click the Free Tab Switcher icon in your Chrome toolbar
- Open βοΈ Default Settings (For New Windows), below the window cards
- Set the Default Cycle Interval in seconds (minimum 10; 60 or more is the most reliable)
- Tick "Auto-start when browser opens". It saves straight away.
Step 2: Make Chrome Open When the Computer Starts
Auto-start runs once Chrome is open. Chrome doesn't open at login by default, and an extension can't switch that on, so it's a one-time setting on the computer. Our FAQ has the steps for Windows, Mac and Linux. From version 2.1, the popup links to the same steps (Show me how, under the auto-start box).
Also set Chrome's On startup option to Continue where you left off, so your tabs come back.
Step 3: Test the Setup
- Close Chrome completely (check Task Manager if needed)
- Reopen Chrome, or restart the computer
- Verify that your tabs come back and start rotating
- Check that the extension icon is in colour (grey means stopped)
π§ What Auto-Start Does
When auto-start is on:
- Every window starts rotating when Chrome opens, at the default interval
- Windows you open later start rotating too
- Manual controls still work: βΉ Stop on a window's card,
Ctrl+Shift+Sto stop every window,Ctrl+Shift+Xto toggle them all
What Auto-Start Doesn't Keep
Changes you make on a window's card (its interval, refresh mode and skipped tabs) last until Chrome closes. After a restart, every window starts again with the default interval, no refresh and no skipped tabs.
Default settings (auto-start and the Default Cycle Interval) are kept across restarts. Window settings override them for one window, until Chrome closes.
To bring back an exact setup on every start (fixed pages, a display time for each, its own monitor, fullscreen), use a Pro playlist with "Launch when Chrome starts" ticked.
ποΈ Advanced Configuration Scenarios
Scenario 1: Digital Signage Display
Goal: Automatically cycle through company announcements, weather, news
Configuration:
β Auto-start enabled
β Default interval: 60 seconds
β Only the display pages open in this window
Setup Steps:
- Open the pages to show in one Chrome window, and nothing else
- Set the Default Cycle Interval to 60 seconds
- Tick "Auto-start when browser opens"
- Make Chrome open when the computer starts (Step 2 above)
- Restart Chrome and check the rotation
Refresh modes reset when Chrome restarts, so pick pages that update themselves. Or use a Pro playlist, where each page can reload when it comes on screen.
Scenario 2: IT Monitoring Station
Goal: Continuous monitoring of server dashboards and alerts
Configuration:
β Auto-start enabled
β Default interval: 30 seconds
β Refresh: after switching (on the window's card)
β Skipped: any tab that isn't a dashboard
Setup Steps:
- Open your monitoring dashboards in one window
- Set the Default Cycle Interval to 30 seconds and tick auto-start
- On the window's card, open Configure⦠and choose "Refresh after switching", so each dashboard reloads as it comes on screen
- Tick "Skip specific tabs when cycling", then tick any tab that isn't a dashboard
- After a restart, set the refresh mode and skips again, or use a Pro playlist to keep them
Scenario 3: Research Workstation
Goal: Background information cycling while working
Configuration:
β Auto-start off
β One window per research topic, each with its own interval
β Manual control when needed
Setup Steps:
- Leave auto-start off
- Open one Chrome window per topic
- Set each window's interval on its card and click βΆ Start when you need it
- Press
Ctrl+Shift+Xto start or stop every window at once
π οΈ Troubleshooting Common Issues
Autostart Not Working
Symptom: Extension doesn't start automatically Solutions:
- Check that Chrome opened by itself: auto-start runs only once Chrome is open. After a reboot, Chrome has to start at login (Step 2)
- Verify Chrome startup: Ensure Chrome is completely closed before testing
- Check the extension is on: Visit
chrome://extensions/and ensure Free Tab Switcher is enabled - Reload the extension: Try disabling and re-enabling it
- Restart browser: Close all Chrome processes and restart
Autostart Working But Wrong Settings
Symptom: Autostart activates but with unexpected configuration Solutions:
- Check the default: after a restart, windows use the Default Cycle Interval, not the interval you last set on a card
- Expect a clean slate: refresh modes and skipped tabs reset when Chrome restarts. Set them again, or use a Pro playlist to keep them
- Change one window: click βΉ Stop on its card, change its settings, then click βΆ Start
Performance Issues with Autostart
Symptom: Browser startup is slow or cycling is laggy Solutions:
- Increase cycle intervals: Try 60+ seconds for resource-heavy sites
- Reduce tab count: Limit to essential tabs only
- Optimize refresh settings: Disable refresh if not needed
- Check tab content: Some sites consume more resources than others
Autostart Conflicts with Other Extensions
Symptom: Autostart interferes with other browser extensions Solutions:
- Check extension conflicts: Disable other tab-management extensions
- Verify keyboard shortcuts: Ensure
Ctrl+Shift+XandCtrl+Shift+Sdon't clash with other extensions (checkchrome://extensions/shortcuts) - Monitor Chrome performance: Use Task Manager to identify resource conflicts
π Best Practices for Autostart
Security Considerations
- Verify tab URLs: Ensure all tabs point to trusted sites
- Monitor network activity: Watch for unexpected network requests
- Use HTTPS sites: Prefer secure connections for sensitive monitoring
- Regular audits: Periodically review which tabs are included in autostart
Performance Optimization
- Minimum intervals: Never go below 10 seconds to avoid overwhelming sites
- Resource monitoring: Use Chrome's Task Manager to watch memory usage
- Tab limits: Keep autostart tab counts reasonable (under 15)
- Network consideration: Factor in slow networks when setting intervals
Maintenance Routine
Weekly:
- Test autostart functionality
- Verify all monitored sites are still accessible
- Check for Chrome and extension updates
Monthly:
- Review and optimize cycle intervals
- Close pages the screen no longer needs
- Check every open tab still belongs on screen
Quarterly:
- Document current autostart configurations
- Evaluate new use cases or workflow changes
- Update the pages for seasonal needs
π Advanced Autostart Techniques
Multiple Monitor Setups
For multi-monitor environments:
- Open separate Chrome windows on different monitors
- Auto-start rotates every window at the default interval. Give a window its own interval on its card; that lasts until Chrome closes
- For screens that come back by themselves, use Pro playlists: each opens on its own monitor, fullscreen, when Chrome starts
- Coordinate cycle timing to avoid simultaneous refreshes
Enterprise Deployment
For IT teams deploying autostart across multiple systems:
- Standardize configurations: Create documented setup procedures
- Copy one setup everywhere: with Pro, Export config and Import config move your playlists and settings to another computer
- Monitor resource usage: Track performance across deployments
- Centralize documentation: Maintain shared configuration guides
π Quick Reference
Autostart Checklist
- [ ] Free Tab Switcher installed and enabled
- [ ] "Auto-start when browser opens" ticked
- [ ] Default Cycle Interval set (minimum 10 seconds)
- [ ] Chrome opens by itself when the computer starts
- [ ] Chrome set to "Continue where you left off"
- [ ] Auto-start tested with a browser restart
Common Intervals by Use Case
- Emergency monitoring: 10-15 seconds
- Active dashboards: 30-45 seconds
- General monitoring: 60-90 seconds
- Background information: 2-5 minutes
- Ambient awareness: 5+ minutes
Troubleshooting Quick Fixes
- Restart Chrome completely
- Disable/enable the extension
- Check that Chrome opens by itself at login
- Check Tab count and reduce if needed
- Verify autostart checkbox is checked
Ready to set up autostart? Follow this guide step-by-step, and you'll have reliable, automatic tab cycling in no time!
Need help? Check our FAQ or reach out through our contact page.
Want to learn more? Explore our related guides:
- From Profiles to Playlists - Save a setup that comes back on its own
- Tab Filtering Guide - Skip tabs and choose which ones refresh
- FAQ - Making Chrome open when the computer starts