<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kite on WebNotes</title><link>https://v2.webnotes.in/categories/kite/</link><description>Recent content in Kite on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/categories/kite/index.xml" rel="self" type="application/rss+xml"/><item><title>Kite chart errors: preference limit, CDN failure, and not-logged-in</title><link>https://v2.webnotes.in/kite-chart-errors/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/kite-chart-errors/</guid><description>&lt;p&gt;&lt;strong&gt;Kite chart errors&lt;/strong&gt; are the messages Zerodha&amp;rsquo;s &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 platform shows when its charting engine cannot save a layout, cannot reach the chart servers, or has lost the authenticated session that charts run on. The three most common are &amp;ldquo;Chart preference limit reached&amp;rdquo;, which means your cloud storage for saved TradingView layouts is full; &amp;ldquo;Failed to connect to CDN&amp;rdquo;, which is a network or DNS fault reaching Zerodha&amp;rsquo;s Cloudflare delivery network; and a chart-level &amp;ldquo;not logged in&amp;rdquo; prompt, which means the chart session has lapsed and needs a fresh login. Each has a different cause and a different fix.&lt;/p&gt;</description></item><item><title>Kite order quantity and value limits: the 1,00,000 quantity cap and the Rs 10 crore value cap</title><link>https://v2.webnotes.in/kite-order-quantity-value-limits/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/kite-order-quantity-value-limits/</guid><description>&lt;p&gt;&lt;strong&gt;Kite order quantity and value limits&lt;/strong&gt; are the two ceilings Zerodha enforces on the size of a single order: a quantity cap of 1,00,000 shares per equity order, with the exchange freeze quantity standing in for derivatives, and a value cap of Rs 10 crore per order in the equity segment. The quantity cap is partly an exchange market-integrity rule and partly a Zerodha rule about order types; the value cap is a Zerodha risk-management policy. An order that breaches either is rejected before it can fill, and the fix in both cases is to split the order into smaller pieces.&lt;/p&gt;</description></item><item><title>Leverage indicator on Kite</title><link>https://v2.webnotes.in/leverage-indicator-on-kite/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/leverage-indicator-on-kite/</guid><description>&lt;p&gt;The &lt;strong&gt;leverage indicator on Kite&lt;/strong&gt; shows the effective leverage of a planned trade, computed as the ratio of notional position value to margin used. It appears on the order ticket alongside the &lt;a href="https://v2.webnotes.in/margin-required-on-order-window-kite/"&gt;Margin required&lt;/a&gt;
 field.&lt;/p&gt;
&lt;h2 id="how-its-displayed"&gt;How it&amp;rsquo;s displayed&lt;/h2&gt;
&lt;p&gt;On the order ticket, the leverage indicator is typically shown as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;ldquo;Leverage: 5x&amp;rdquo; (or similar).&lt;/li&gt;
&lt;li&gt;A multiplier indicating how much of a position you can take per Rs of margin.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For a scrip with 15% margin requirement, leverage = 100/15 ≈ 6.7x.&lt;/p&gt;</description></item><item><title>How to fix Kite charting and streaming lag on Zerodha</title><link>https://v2.webnotes.in/how-to-fix-kite-charting-lag/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-fix-kite-charting-lag/</guid><description>&lt;p&gt;&lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 uses WebSocket connections to deliver real-time streaming quotes to the browser and to update live candles on charts. Charting and streaming lag, frozen prices, delayed candle updates, or charts that do not load, can originate from Zerodha&amp;rsquo;s servers, your internet connection, your browser, or your device. Identifying the root cause is the essential first step.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Conflict-of-interest disclosure.&lt;/strong&gt; This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.&lt;/p&gt;</description></item><item><title>How to whitelist Kite IPs on a corporate network</title><link>https://v2.webnotes.in/how-to-whitelist-kite-ips-corporate-network/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-whitelist-kite-ips-corporate-network/</guid><description>&lt;p&gt;&lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Zerodha Kite&lt;/a&gt;
 is a browser-based and mobile trading platform that communicates with &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&amp;rsquo;s&lt;/a&gt;
 servers over HTTPS and WebSocket connections. Corporate networks often block non-business web traffic through firewalls, web proxies, or URL filtering systems. If Kite is inaccessible or partially functional on a corporate network, the likely cause is that one or more required domains or connection types are blocked.&lt;/p&gt;
&lt;p&gt;This guide is addressed to both individual users who want to request a firewall change from their IT department and to IT administrators implementing the whitelist.&lt;/p&gt;</description></item></channel></rss>