Many traders assume a trailing stop will always protect a position even if they close their trading platform. Whether that happens depends on how the trailing stop is implemented: some trailing orders are managed by the broker’s servers and remain active when your computer is off, while others require the trading application or a piece of client-side code to keep running. This article explains the two approaches, gives practical examples, and shows how to confirm which behavior your broker provides. Trading carries risk; nothing here is personal advice.
Server-side vs client-side trailing stops — what’s the difference?
When you place a trailing stop you are asking for an exit that moves with the market. The key technical distinction is where the logic that updates the stop lives.
A server-side trailing stop is handled entirely by the broker’s systems. The broker’s matching engine or order-management servers watch market prices, recalculate the stop trigger as the market moves, and submit the closing order when the trigger is reached. Because the broker’s infrastructure is always online, a server-side trailing stop remains active whether your desktop terminal, phone or home computer is connected or not.
A client-side trailing stop is executed by software running on your device. That can be your desktop terminal, a charting app with “drag stop” features, or an Expert Advisor / script that updates a plain stop order as prices change. If the program that contains the logic is closed or your machine loses its connection, the trailing behavior stops updating. The order left on the exchange may then simply be the last stop level that was pushed to the broker, with no further trailing.
How each order type behaves in practice
Brokers typically offer both simple trailing stop orders and variants such as trailing stop-limit. With a server-side trailing stop the server tracks the highest (or lowest) price since the order was posted and sets the trigger at a fixed distance behind that peak. When the trigger is hit the broker converts the conditional into a market or limit order according to the order type you chose.
For example, imagine you buy EUR/USD at 1.2000 and enter a sell trailing stop of 50 pips. If the broker implements the trailing stop on its server, the stop will start at 1.1950, then move up to 1.2050 if price reaches 1.2100, and so on. If your desktop closes, the broker still tracks price and will execute the stop if price falls to the current trigger.
Contrast that with a client-side implementation: you create a regular stop at 1.1950 and run an EA on your PC that updates the stop to 1.2050 as price reaches new highs. If you shut the PC or lose the connection, the EA cannot update the stop level further; the order remains at whatever level it last sent to the broker.
A trailing stop-limit works similarly but submits a limit order when triggered. That gives control over execution price but can fail to fill if the market gaps through your limit.
How to tell whether your broker runs trailing stops server-side
The simplest way to find out is to check the broker’s order-type documentation and test in a safe environment. The documentation should state whether trailing orders are processed on the broker’s servers or require the client application. If documentation is unclear, use a small live or demo trade to test.
A practical test: open a small position, place a trailing stop, then completely close or disconnect your desktop terminal and monitor the position through the broker’s web or mobile portal (or let the test run in a demo account). If the stop continues to move with new highs and triggers as expected, it’s server-side. If it freezes at the last level the terminal set, the trailing logic was client-side.
You can also ask client support and mention the specific order type (e.g., “trailing stop” vs “trailing stop limit” vs “OCO”) and the instrument you want to trade. Some instruments or market sessions (like extended hours) may be treated differently.
Options if your broker doesn’t offer server-side trailing stops
If your broker does not provide server-side trailing stops but you need always-on automation, there are two common alternatives. One approach is to run your trailing logic on a cloud server or VPS that you control. Using the broker’s API (REST, FIX, or native API), your cloud process can subscribe to market data and update stop orders continuously; because the cloud instance runs 24/7, the trailing behavior persists even when your desktop is off.
The other approach is to use broker-supported conditional or OCO order types that the server will honor. Some platforms offer conditional templates (for example, exit on underlying price or an OCO between a profit target and a stop) that are evaluated server-side and therefore remain active. If your strategy can be expressed with those server-side conditionals you avoid managing your own infrastructure.
Concrete example: trailing stop vs trailing stop-limit
Imagine a stock bought at $100 and you set a $2 trailing stop as a server-side order. The server sets the stop at $98. If the stock rises to $110 the server moves the stop to $108; if the stock then falls to $108 the server submits a market sell order and execution follows.
Now suppose you selected a trailing stop-limit with a $2 trail and a $1 limit offset. At $110 the server would set a stop at $108 and a limit at $107 (stop minus offset). If the stock falls quickly through $108 to $106, the limit order at $107 may never fill and you can be left exposed. A server-side trailing stop-limit stays in force, but you must accept the possibility of no execution if the market gaps past your limit.
Practical checks and setup steps
When you plan to rely on trailing stops while away from your desktop, take these steps before trading live. First, confirm in writing (support chat or documentation) whether the specific trailing order type is handled server-side. Second, run a demo or small live test to confirm behavior across market conditions. Third, if you need always-on automation and the broker lacks server-side trailing, decide whether you will run your own VPS using the broker API or use conditional server-side order templates offered by the broker. Finally, review how the broker treats extended-hours trading, instrument coverage, and how stop triggers are calculated (last trade, bid/ask, or midpoint).
Quick checklist to verify server-side trailing stops:
- Confirm order-type behavior in the broker’s documentation or support.
- Run a demo test: place a trailing order and close your terminal.
- Check execution behavior and whether the stop continues to trail and trigger.
Risks and caveats
Even when a trailing stop is server-side, it is not a guarantee of price. A server-side trailing stop that converts into a market order will execute at the prevailing price, which can be above or below the trigger during fast moves, causing slippage. A trailing stop-limit protects against execution worse than your limit but introduces the risk of not filling at all if the market moves past the limit. Some instruments or extended trading sessions do not support certain trailing order types, and brokers may calculate triggers using different price fields (last, bid, ask, or consolidated feed), so results can vary.
If you implement your own automation via a VPS and an API, you introduce operational risks: your code may have bugs, the VPS or API can suffer outages, and you may face delays or rate limits in market data or order submission. Running server-side automation also increases complexity and potential costs. Finally, relying solely on automation without periodic human oversight can be dangerous during unexpected market events; always design fallback procedures and monitor critical systems.
Final notes
Many brokers do provide true server-side trailing stops that remain active when your desktop is closed, but the feature, limits, and exact behavior vary. Don’t assume all “trailing” functions are server-managed. Verify order-type behavior, test before depending on it with real capital, and consider server-based automation or broker conditionals when you need continuous, always-on management.
Key takeaways
- Confirm whether the broker’s trailing order is processed server-side or requires your client app; documentation and a small demo test will show the difference.
- Server-side trailing stops remain active when your desktop is closed; client-side trailing requires your program to run continuously.
- Even server-side orders are subject to slippage, gapping, and instrument/session limitations; trailing stop-limit orders can fail to fill.
- If your broker lacks server-side trailing, consider running automation on a VPS via API or using server-side conditional orders — but be aware of operational risks.
References
- https://www.interactivebrokers.com/campus/trading-lessons/trailing-stop/
- https://highstrike.com/trailing-stop/
- https://acy.com/en/market-news/education/trailing-stop-loss-strategy-144647/
- https://www.schwab.com/learn/story/trailing-stop-orders-mastering-order-types
- https://www.interactivebrokers.com/campus/trading-lessons/trailing-stop-limit/
- https://tradenation.com/articles/what-is-a-trailing-stop-order/
- https://us.etrade.com/knowledge/library/options/automating-exit-strategies-for-options-trades