Time In Force Orders Explained: GTC, IOC, FOK, And Post-Only

You can pick the "right" buy or sell button, and still get a result you didn't mean. The usual reason is not the market being unfair, it's the time in force orders setting being misunderstood (or left on a default you didn't notice). Time-in-force (TIF) is basically your order's "life rules". It tells the matching engine how long your order can stay active, and how strict it should be about filling right now. Once you see TIF as a constraint, not a strategy, a lot of execution surprises starts to look avoidable. Time in force is a rule on the order, not the order type Infographic summarizing common time-in-force instructions and how they behave in an order book, created with AI. A lot of traders mix two separate ideas: Order type: market, limit, stop, stop-limit (how the price and trigger works). Time in force: GTC, Day, IOC, FOK, Post-Only (how long it lives, and how it's allowed to execute). For example, "IOC" doesn't mean "buy fast." It means: "Try to execute immediately, then cancel the rest." You can place an IOC limit, and it still won't pay above your limit. Same with FOK, it's a fill condition, not a price instruction. If you want a clean baseline definition from a neutral source, Investopedia's explanation of time in force matches how most brokerages and exchanges label it (even if the exact options differ by venue). Also, don't ignore the platform layer. Some apps show TIF only after you switch to "advanced." Others hide it behind a small dropdown. In crypto, this is common. If you're still sorting out the basic buttons first, this guide on choosing limit, market, stop orders helps separate "type" from "timing," before TIF even enters the story. Keep one tiny order book in your head (it makes TIF feel obvious) Example order book ladder with bids and asks near the current price, created with AI. Picture a simplified BTC/USDT order book: Best bid: $50,000 for 1.2 BTC Next bid: $49,990 for 0.8 BTC Best ask: $50,010 for 1.5 BTC Next ask: $50,020 for 1.0 BTC Now you place a limit buy for 2.0 BTC at $50,010. Your price is high enough to trade with the ask side. But what happens depends on TIF: With IOC, the engine grabs what it can now (up to 2.0) and cancels what remains. With FOK, it must get the entire 2.0 immediately, or it cancels the whole thing. With GTC, any unfilled portion can sit on the book (if your limit is not marketable anymore after partial fill). This is why TIF matters more when liquidity is thin, spreads are wide, or your size is not "tiny." In a deep market, all of this feels boring. In a choppy session, it becomes the difference between a controlled entry and a messy average fill. A simple mental check: order type decides "at what price rules," time in force decides "for how long and how strict." GTC vs IOC vs FOK: what really changes, with short fill examples Most platforms offer more than these, like Day, GTD (good-till-date), or session-based rules. Still, GTC, IOC, and FOK are the core set you keep meeting across stocks and crypto. Exchanges may describe these mechanics in different words, but the logic is consistent, you can also compare it with a market-structure style reference like the TSX order types and functionality guide (it's equities-oriented, but the matching ideas carry over). Here's a quick comparison before we go into mini-scenarios: TIF What it means Partial fills? If not fully filled right away Typical use GTC Good-Till-Canceled Yes Rests until filled or you cancel (or venue expires it) Planned entries, passive exits IOC Immediate-Or-Cancel Yes Fills what's available now, cancels the remainder Grab liquidity without lingering FOK Fill-Or-Kill No (all-or-nothing) Cancels entirely if full size can't fill now Exact size requirement Day (common) Valid for today's session Yes Cancels at session end if not filled Avoids "forgotten" orders Now the same order book again. You submit buy 2.0 BTC at $50,010. IOC example (partial is allowed): Best ask is $50,010 for 1.5 BTC. The engine fills 1.5 at $50,010. The remaining 0.5 BTC is canceled instantly. You're in, but not full size. FOK example (partial is not allowed): Only 1.5 BTC is available at your price level. Even if 0.5 exists at $50,020, your limit blocks paying higher. Result is: cancel everything, zero fill. GTC example (order can persist): If 1.5 BTC fills at $50,010 and your remaining 0.5 is still priced at $50,010, it might rest as a bid (depending on how the book moved). You may get filled later, or you may sit there until you cancel. So the hidden question is not "will I get filled." It's "am I okay with a half fill," and "do I want leftovers sitting around while I'm not watching." Post-only: maker protection that can cancel (or reprice) your order "Post-only" often gets treated like a bonus option. In reality it's a strict promise you make to the matching engine: do not execute immediately. The order must add liquidity (maker), or it must be rejected or canceled. In plain terms, post-only is like walking to the queue instead of cutting to the front. If your price would cross the spread, you're trying to take liquidity. The engine says no. A quick scenario: Best bid: $50,000 Best ask: $50,010 You place post-only limit buy at $50,010 for 1.0 BTC That price is marketable because it can match the best ask. A post-only order can't do that, so venues handle it in one of two ways: Cancel or reject the order ("post-only would execute immediately"). Auto-reprice it by one tick to keep maker status (common on some venues, not universal). This is why post-only "protects maker status," but it also protects you from yourself when you thought you were placing a resting limit, yet your limit was actually aggressive. The behavior is exchange-specific, and some platforms document the difference clearly, see this practical page on GTC, IOC, FOK, and post-only behaviors for a crypto-oriented view. If you want the real-world failure cases (rejections, partial weirdness, and fee side effects), this XXKK guide on post-only orders in crypto trading spells out the common messages traders keep seeing and misreading. Post-only is not for emergencies. If you need out now, forcing maker behavior can mean no fill, while price keeps moving. A quick pre-trade checklist (plus a short risk note) Before you hit submit, pause for 10 seconds. That pause is cheaper than "learning fees." Session and market state: Is it a normal session, or thin after-hours, or a news candle? Liquidity check: Look at spread and top-of-book size, not only the last price. Urgency: Do you need a fill now, or do you just want a price level? Fee impact: Will this likely be maker or taker, and do you care today? Slippage risk: If it's a marketable order, can it sweep multiple levels? Partial-fill tolerance: Are you okay with 30% filled and 70% canceled (IOC)? All-or-nothing need: If your plan breaks with partial size, consider FOK (and accept zero fill). Leftover order risk: If you might forget it, Day can be safer than GTC. Risk note: Trading can produce losses fast, especially with leverage and thin books. Even "safe" settings can fail during gaps, halts, or sudden volatility. Use smaller size while you test how your venue applies TIF rules. Conclusion Time in force orders look like a small dropdown, but they decide how your order behaves when the market doesn't cooperate. GTC is patience, IOC is "take what's there," FOK is strict all-or-nothing, and post-only is a maker-only promise that can cancel or adjust your order depending on venue rules. If you remember one thing, remember this: order type controls price logic, while time in force controls execution rules. Get both aligned, and your fills start to feel less random.