How to Add a Screenshot to a ServiceNow Ticket

To add a screenshot to a ServiceNow ticket, open the record, select its paperclip or attachments control, choose the screenshot file, click Attach, and close the attachment window. The file should appear in the record’s attachment list. Directly pasting an image into a ticket field is not a reliable, supported way to attach it.

This guide covers the standard workflow for incidents and other records, how to prepare the file, what to check when an upload fails, and how to confirm that the right people can access the attachment. Labels and placement can vary by ServiceNow release, workspace, browser, and organization settings.

1. Attach a screenshot to an existing ticket

1. Open the ServiceNow incident, change, problem, or other ticket record you want to update. You need permission to edit the record, and attachments must be enabled for your instance.
2. Find the paperclip or Attachments control on the record form. Some interfaces label it Manage Attachments. On a form, it is commonly near the top of the record, but the exact location depends on the interface.
3. In the attachment window, choose Choose Files or Browse. The button label depends on your browser.
4. Select the screenshot image from your device and confirm the selection.
5. Click Attach. Wait for the upload to finish. The file should appear in the Current file attachments list and at the top of the form.
6. Click Close to close the attachment window. Save or update the ticket if your workflow requires it, then verify that the attachment is still shown on the record.

ServiceNow’s documented attachment flow uses the attachments control on the record form and then the file chooser and attach action. If your screen uses different labels, look for the paperclip or attachment management action on the record. [ServiceNow documentation: Add and manage attachments]

2. Prepare the screenshot before uploading

A useful attachment makes the issue easier to diagnose without exposing unrelated information. Before you upload:

• Capture the relevant state. Include the error, page, or control the ticket concerns. If context matters, include enough of the surrounding screen to show where it occurred.
• Check for sensitive data. Crop or redact passwords, access tokens, personal data, customer details, or internal information the ticket audience should not see. Do not assume that every person who can access the ticket has the same permissions as you.
• Use a permitted image format. The instance may restrict extensions or MIME types. If an upload is rejected, try an image format allowed by your organization rather than repeatedly renaming the same file.
• Keep the file practical in size. Large screenshots take longer to upload and may exceed an instance’s configured limit. Crop unnecessary areas or save a reasonably sized image when appropriate.
• Use a descriptive filename. A name such as checkout-error-2026-09-30.png is easier to identify later than Screenshot 1.png. Avoid putting confidential details in the filename.

ServiceNow states that the default maximum attachment size for a new out-of-box AI Platform instance is 1024 MB (1 GB). Administrators can configure attachment size, allowed extensions, and MIME validation, so an individual organization’s effective limits may be lower. [ServiceNow documentation: attachment properties]

3. Can you paste a screenshot into ServiceNow?

Do not rely on copying an image and pasting it directly into a ticket field. ServiceNow employee guidance says image copy-and-paste is not a supported function across the combinations of browser, device, form view, user interface, and HTML field that customers may use. Behavior can vary, and a pasted image may not become an attachment.

Use the paperclip or attachment management workflow when the goal is to add an image file to the ticket. If your organization has a specific editor or workflow that supports inline images, follow its documented process and confirm the image is saved and visible after updating the record. For a normal ticket attachment, choose the file and click Attach. [ServiceNow Community guidance on attaching screenshots]

4. Confirm the attachment and its audience

After attaching, check that the filename appears in the record’s attachment list. If possible, reopen the record or refresh it and confirm the attachment remains. This catches cases where a window was closed before the upload finished or the record update did not complete.

Do not assume an external requester can view the file just because an agent can. Access to attachments in a Service Portal can depend on authentication, portal behavior, and instance configuration. If the requester is outside your ServiceNow login boundary, verify visibility using the relevant portal or ask an administrator to confirm the access settings. Keep sensitive content out of attachments that may be exposed to a broader audience. [ServiceNow Service Portal attachment guidance]

5. Interface differences to expect

What may differ	What to look for
Control label	Attachments, a paperclip icon, or Manage Attachments.
Record state	Some workflows expect the record to exist before you attach. If a new ticket is not yet saved, save it first and then attach.
Attachment location	The current file list may be in a dialog or displayed near the top of the form.
Permitted files	Allowed extensions, MIME types, and maximum size are controlled by instance settings and policy.
External visibility	Portal users’ ability to open attachments depends on authentication and access configuration.

If the control is missing, the attachment feature may be unavailable in that view, hidden by the interface, or restricted by your role or instance configuration. Check the record form and your organization’s instructions; an administrator can confirm permissions and attachment settings.

6. Troubleshooting upload problems

Symptom	Likely cause	What to try
The paperclip or attachment action is missing	The current view, role, or record configuration does not expose attachment management.	Open the full record form, look for Manage Attachments, and ask an administrator whether your role and this record type permit attachments.
The file chooser opens, but the file is rejected	The extension or detected MIME type is prohibited.	Use an allowed image type and check your organization’s file policy. Renaming an unsupported file does not change its actual format.
The upload reports that the file is too large	The file exceeds the configured maximum for the instance or request path.	Crop, resize, or compress the screenshot when image clarity permits. Ask the administrator for the configured attachment limit; the documented out-of-box default is not a guarantee of your instance’s limit.
The upload appears stuck or fails without a clear message	The connection may have interrupted, the browser may have blocked the action, or the instance may have rejected the request.	Wait for the upload to finish, retry once on a stable connection, and check whether the file appears in the attachment list before attempting another upload. If it continues, note the filename, size, browser, and any error text for your ServiceNow support team.
The attachment window closes but the file is absent	The upload may not have completed, or the ticket update may not have been saved.	Reopen attachments and check the current-file list. Attach again only if the file is absent, then save or update the record if required.
An external requester cannot open the image	The portal may require authentication, or attachment access may be restricted.	Confirm portal and attachment access rules with an administrator. Do not send a sensitive screenshot through a less controlled channel as a workaround.
Pasting an image does nothing	Copy-and-paste behavior is unsupported or varies with the browser, device, form, and field.	Save the screenshot as an image file and use the paperclip attachment workflow.

Administrators manage attachment restrictions through attachment and security properties. When escalating, include the record type, the approximate file size, the file extension, the exact error, and whether other allowed files attach successfully. Avoid including secrets or sensitive screenshots in the support request itself unless its audience is appropriate.

7. Capture a screenshot for a ticket with code

If the screenshot should come from a web page rather than your desktop, a browser automation script can capture it to a file. The example below uses Playwright in Python, opens a page, waits for it to load, and writes a PNG. Install Playwright and its browser once, then run the script locally.

python -m pip install playwright
python -m playwright install chromium

from pathlib import Path
from playwright.sync_api import sync_playwright

url = "https://example.com"
output = Path("page-screenshot.png")

with sync_playwright() as p:
    browser = p.chromium.launch(headless=True)
    page = browser.new_page(viewport={"width": 1440, "height": 900}, device_scale_factor=1)
    response = page.goto(url, wait_until="networkidle", timeout=60000)
    if response and response.status >= 400:
        raise RuntimeError(f"Page returned HTTP {response.status}")
    page.screenshot(path=str(output), full_page=True)
    browser.close()

print(f"Saved {output}")

Use a URL you are permitted to access. For pages that keep background network connections open, networkidle may not occur; replace it with wait_until="domcontentloaded" and, if needed, wait for a specific selector before capture. A full-page capture can be much taller and larger than the visible viewport. Inspect and redact the output before attaching it.

To attach the generated file, return to the ticket and follow sections 1 and 2. The capture script does not log into ServiceNow or upload to a ticket: authentication, record permissions, and attachment policy remain governed by the ServiceNow instance.

8. Or skip the browser setup

If the source is a public web page, ScreenshotNeo can return a screenshot from one API request. Its API can capture PNG, JPEG, WebP, or PDF; the following request saves a WebP response. Review the ScreenshotNeo API documentation for access-key setup and request options, then attach the downloaded file to ServiceNow using the standard workflow above.

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

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Review the returned file before adding it to a ticket, especially if the page contains information that should not be shared.

Sign up for 1,000 free screenshots a month, with no card required.

9. Performance, reliability, and cost considerations

For a single ticket, the built-in attachment control is usually the shortest path: it avoids setting up browser tooling or an API account. The main practical constraints are file size, network stability, allowed formats, and whether the ticket’s audience can access the file.

For repeated captures of public pages, browser automation adds a browser installation and needs enough time for the page to load. Full-page screenshots may consume more memory and produce larger files. Set a timeout, choose a clear wait condition, close the browser after capture, and check the file before attaching it. A timeout does not establish that the page itself is unavailable; the selected wait condition may simply be unsuitable.

ScreenshotNeo pricing is Free for 1,000 shots per month, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free, and every feature is on every plan. Its billing rules state that only clean shots are billed, while bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; responses include X-Page-Verdict and X-Billed headers. These API costs are separate from any costs or policies attached to a ServiceNow instance. Keep API keys out of source control and avoid exposing private ticket URLs or page credentials in logs.

10. Quick checklist

• Open the intended record and confirm you have permission to edit it.
• Use the paperclip or attachment control, then choose the image file and click Attach.
• Wait for the upload and verify the filename appears in the attachment list.
• Save or update the record when your workflow requires it.
• Check size, file type, and audience access if the upload fails or the requester cannot view it.
• Remove or redact sensitive information before sharing the image.

11. FAQ

Does adding an attachment automatically notify the requester?

That depends on your organization’s ServiceNow workflow and notification rules. Check the record activity and local process rather than assuming the attachment triggered a message.

Can I attach a screenshot to an incident I have not submitted yet?

Some workflows require the record to be saved first. If the attachment control is unavailable on a new form, save or submit the record according to your process, reopen it, and attach the file.

Will every customer be able to see the screenshot?

No universal visibility promise can be made. Access depends on the portal, authentication, and instance configuration; verify it for the intended audience.

What should I send support when an upload keeps failing?

Share the error text, record type, browser, file extension, and approximate size. Follow your organization’s rules for sharing logs, and do not include confidential screenshot contents unless the support channel is authorized for them.