How to Take a Screenshot of an Indian Broker Dashboard After Login with OTP

To capture an Indian broker dashboard after login with OTP, sign in through the broker’s official app or website, complete the second factor it requests, open the dashboard, and use your phone or computer’s built-in screenshot control. The exact login steps and screenshot shortcut depend on the broker, device, and operating system.

Before saving or sharing the image, check what it reveals. Use the broker’s privacy mode if available, and crop or redact account information the recipient does not need. Never include or share your password or OTP.

1. Sign in through the broker’s official channel

1. Open the broker’s official app or type its official website address yourself. Avoid sign-in links from unsolicited messages.
2. Enter the credentials requested by the broker.
3. Enter the OTP or complete the other second factor shown in the broker’s login flow. Do not share the code with anyone.
4. After authentication, navigate to the dashboard or the specific account page you need to capture.

Login flows differ. For example, Zerodha’s Kite app instructions describe entering a registered phone number or user ID and password, then the OTP received by SMS or email. Its instructions say to enter the second factor within five minutes of entering the login credentials. Kite may then ask the user to confirm with a device lock PIN, biometric, or pattern. These are Kite-specific details, not a universal flow for Indian brokers. See [Zerodha’s Kite app login instructions](https://support.zerodha.com/category/your-zerodha-account/login-credentials/login-credentials/articles/how-to-login-to-kite-app).

2. Reduce sensitive information before capture

If the broker provides a privacy mode, consider enabling it before capturing a dashboard that contains balances, holdings, positions, or funds. Check the screen afterward: a privacy mode may hide only certain information or pages.

On Kite web, Zerodha documents a privacy mode for Dashboard, Holdings, Positions, and Funds. Its instructions say to click the user ID and select the privacy-mode toggle. On the Kite app, Zerodha documents privacy mode for Holdings, Positions, and Funds; disabling it requires biometric authentication or 2FA. These controls and covered screens are specific to Kite and may change. Refer to [Kite web privacy mode](https://support.zerodha.com/category/trading-and-markets/kite-web/kite-web-user-manual/articles/privacy-mode-on-kite-web) and [Kite app privacy mode](https://support.zerodha.com/category/trading-and-markets/kite-mobile/kite-mobile-user-manual/articles/privacy-mode-on-kite-mobile).

Privacy mode is not a substitute for reviewing the image. Before sharing, inspect the full screenshot for names, account identifiers, balances, order details, browser tabs, notifications, or other information that is unnecessary for the recipient.

3. Capture with your device’s screenshot control

Use the screenshot function built into the device on which the dashboard is displayed. The title does not specify a device or operating system, so there is no single shortcut or gesture that applies to everyone. Look up the screenshot instructions for your exact phone or computer and OS version if you do not know the control.

• On a phone: capture the current screen using the device’s screenshot gesture or button combination. The image is typically saved to the device’s photo or screenshot library.
• On a computer: use the operating system’s screenshot tool or keyboard shortcut. Choose a selected-area capture if you need only the dashboard region.
• For a long page: if the device offers scrolling or full-page capture, review whether the broker page supports it. A normal screenshot captures only visible content.

After capture, open the saved image and confirm it is legible, complete enough for its purpose, and free of information you did not mean to disclose. Crop or redact unnecessary details before sending it.

4. Sharing a screenshot safely

• Share only the portion needed to explain the issue or provide the requested record.
• Remove or cover account identifiers and financial details that the recipient does not need.
• Do not send an OTP, password, recovery code, or an image that exposes one.
• If contacting support, follow the broker’s official support instructions. A request for a screenshot of an error message does not automatically require sending the entire dashboard.

Zerodha’s terms state that login and 2FA credentials are confidential and must not be shared with third parties. NSE’s My Portfolio service has its own OTP and credential guidance; it is a separate facility, not a broker login process. See [Zerodha’s account terms](https://zerodha.com/terms-and-conditions) and [NSE My Portfolio terms](https://www.nseindia.com/invest/investors/my-portfolio-terms-and-conditions).

5. If you need a browser screenshot in code

For a dashboard you are authorized to access, an automated browser can sign in and capture a page after you complete the broker’s supported authentication flow. Do not try to bypass OTP, CAPTCHA, bot checks, or other access controls. Broker login pages may block automation or prohibit it under their terms. Never put OTPs or account passwords in source code, logs, screenshots, or shared automation output.

A safe general approach is to use the broker’s documented API or export facility when it meets your need. If you use browser automation, keep credentials in a secret store, restrict access to the resulting image, and require a human to complete interactive authentication where necessary. Do not automate or store credentials unless the broker permits that use.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. For a public page or a page you are authorized to capture, one GET request can return an image or PDF. It cannot replace the broker’s OTP login flow: do not send broker credentials or OTPs to a screenshot service. For protected dashboards, use the broker’s permitted access method and follow its terms.

For a URL that does not require private broker authentication, this cURL example saves a WebP screenshot:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

See the ScreenshotNeo API documentation for supported parameters. Cookie banners, popups, and chat widgets are removed before capture; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. Sign up for free and get 1,000 screenshots a month with no card.

Troubleshooting

Problem	Likely cause	What to do
The OTP is rejected or has expired	The code may have expired, been entered incorrectly, or come from a different login attempt.	Request or use the current code through the broker’s official flow. Follow that broker’s timing instructions; do not reuse an old code or share it.
The dashboard is still loading	Authentication may not have completed, or the page may still be loading data.	Wait for the dashboard to finish and verify the expected account and page before capturing. If it remains stuck, use the broker’s official help channel.
The screenshot shortcut does nothing	Shortcut behavior varies by device, operating system, keyboard, and app.	Use the built-in screenshot utility or consult the device maker’s instructions for your exact model and OS.
Part of the dashboard is missing	A regular screenshot captures the visible screen, not necessarily the full page.	Scroll and capture additional sections, or use a built-in full-page capture option if your device and page support it. Check that the saved result contains what you need.
Sensitive figures remain visible	Privacy mode may not cover that page or every field.	Inspect the screenshot, then crop or redact the unnecessary details. Do not assume privacy mode hides everything.
Support asks for a screenshot	The request may concern an error or a specific screen.	Confirm the request came through an official support channel. Send only the relevant error or page area, after removing unrelated account information.

Performance, reliability, and cost

A built-in screenshot is usually the simplest option for a one-time capture because it records the screen already open on your device. Its limitations are practical: the displayed area may not include a long page, notifications or browser chrome may appear, and data that has not loaded yet will not be captured.

For repeated workflows, first check whether the broker provides an official API, report, or export that is permitted for your use. Browser automation can be sensitive to login changes and interactive security checks, so it needs careful handling and should not circumvent those controls. The cost of a manual screenshot depends on the device and service you already use; no special screenshot hardware is required for the steps above.

FAQ

Can I take the screenshot before entering the OTP?

You can capture a login screen, but it will not show the authenticated dashboard. Complete the broker’s requested authentication first if the dashboard is what you need.

Is privacy mode available with every Indian broker?

The research here verifies examples for Zerodha Kite web and app only. Check your broker’s own help pages and inspect the captured image.

Can I use a screenshot API for my logged-in broker dashboard?

Only if the broker permits the method and the service can access the page without receiving credentials or bypassing security controls. Do not submit an OTP or password to ScreenshotNeo; its URL screenshot request is suited to pages you can capture without handing over private login credentials.

Should I send the whole dashboard to support?

Only if the broker’s official support process specifically requires it. Usually, share the relevant error or cropped area and remove unrelated financial or account details.