To share console logs with a developer, open your browser's console (Chrome and Firefox: press the keyboard shortcut; Safari: turn on the Develop menu first), reproduce the bug so the red error lines appear, then either copy the text into a message or take a screenshot that shows the whole console. That's it — no coding needed.

A "console log" is just the browser's behind-the-scenes diary. Every website quietly writes notes there while it runs, and when something breaks it usually leaves a red error line explaining what went wrong. You can't see this diary during normal browsing, but developers rely on it to fix bugs fast. If a developer asked you to "send the console errors," they want a copy of those notes from the moment the problem happened.

This guide gives you the exact menu paths and keyboard shortcuts for Chrome, Firefox, and Safari, tells you precisely what to copy or screenshot, and ends with a one-link shortcut plus a ready-made message support teams can paste to their own customers.

The 60-second version

If you only remember one thing, remember this order:

  1. Open the page where the bug happens.
  2. Open the console (shortcuts below).
  3. Do the thing that breaks — click the button, submit the form, load the page again.
  4. Copy the red lines or screenshot the whole console.
  5. Paste it into your reply to the developer.

The reason step 3 matters: the console only records an error as it happens. If you open the console after the bug, the useful lines may already be gone. Reproduce the problem with the console already open.

How to open the browser console in Chrome

Chrome is the most common browser, so start here.

  • Keyboard shortcut: press Ctrl + Shift + J on Windows/Linux, or Cmd + Option + J on Mac. This opens straight to the Console tab.
  • No shortcut? Right-click anywhere on the page, choose Inspect, then click the Console tab at the top of the panel that appears.

Now reproduce the bug. Red lines with a small ⊘ icon are errors — those are what the developer needs. Yellow lines are warnings (send them too if you're unsure).

To copy the errors in Chrome:

  • Click just before the first error, drag to select the lines you want, right-click, and choose Copy. Paste into your message.
  • To capture everything at once, right-click any message and choose Save as… — Chrome saves the whole console to a .log text file you can attach.

Chrome's official DevTools Console documentation has screenshots if you get stuck.

How to open the browser console in Firefox

  • Keyboard shortcut: press Ctrl + Shift + K on Windows/Linux, or Cmd + Option + K on Mac.
  • From the menu: click the ☰ menu (top-right) → More tools → Web Developer Tools, then select the Console tab.

Reproduce the bug so the errors appear.

To copy the errors in Firefox:

  • Right-click anywhere in the list of messages. Choose Export Visible Messages to Clipboard to copy everything, then paste into your message.
  • Or choose Save All Messages to File to save a text file you can attach.

Mozilla's Web Console guide documents every button in that panel.

How to open the browser console in Safari (Mac)

Safari hides its developer tools by default, so there's one extra setup step the first time.

Turn on the Develop menu (do this once):

  1. Open Safari and click Safari in the top menu bar → Settings.
  2. Click the Advanced tab.
  3. Check the box Show features for web developers (older Safari calls it "Show Develop menu in menu bar").

Then open the console:

  • Keyboard shortcut: press Cmd + Option + C. This opens the JavaScript Console.
  • From the menu: click Develop in the top menu bar → Show JavaScript Console.

Reproduce the bug, then select the error lines and press Cmd + C to copy, or right-click and choose Save as… to keep a file. Apple's Safari developer tools guide covers the Develop menu in detail.

On iPhone and iPad you can't open the console directly — you have to connect the device to a Mac. If you're on mobile, the screen-recording shortcut further down is the easier path.

What to actually send (the checklist)

The console can look overwhelming. Developers do not need all of it. Send:

  • The red error lines, in full. Don't cut them off — the long path and numbers at the end (the "stack trace") are the most useful part.
  • The URL where it happened. If your screenshot shows the address bar, even better.
  • What you did right before the error: "I clicked Save on the checkout page."
  • The time, roughly, so they can match it to server logs.

Two ways to package it:

Copy-paste (best for developers who want to search the text): paste the copied lines into your message or a plain text file. If it's more than a few lines, attach it as a .txt or .log file instead of pasting a wall of red into chat.

Screenshot (best when you're not sure what to select): capture the whole console panel, not just one line. On Mac press Cmd + Shift + 4 and drag a box; on Windows press Windows + Shift + S. Make sure the red errors and the page URL are both visible. The MDN console reference explains what each message type means if you want to understand what you're looking at.

The common mistake is sending a screenshot of the website instead of the console. The website shows the symptom; the console shows the cause. Developers need the cause.

The steps above work, but they ask a non-technical person to open a hidden developer panel, understand which lines matter, and package them correctly — under pressure, while something is broken. That's a lot.

Here's the shortcut. Instead of opening the console yourself, record your screen while the bug happens and let the tool grab the console for you.

With Clipy's free Chrome extension, you click record, reproduce the bug, and click stop. Clipy captures the browser console automatically in the background, so the single share link you send contains the video and the console logs. The developer opens one link and sees exactly what you saw plus the errors underneath — no "can you open DevTools and paste the red lines" back-and-forth.

Why this is easier for support teams and end users:

  • Nothing to open. No Develop menu, no keyboard shortcuts, no guessing which lines matter.
  • One link, not three attachments. The video, the console logs, and a written summary live at the same URL.
  • It works after the fact. You don't have to know a developer will ask — the recording already has the context.

Clipy is free forever with unlimited recording length, HD up to 4K, and no watermark. You only sign in (one click, Google) to save and share a link. For the developer-facing walkthrough of what ends up in the link, see how to record your screen with console logs.

Copy-paste message for support teams

If you run a support inbox and keep asking customers for console logs, stop writing that request from scratch. Paste this friendly message into your reply — it walks a non-technical customer through the fastest path without jargon:

Hi — thanks for flagging this. To help our engineers fix it quickly,
could you send us the browser's error report from when it broke?

Easiest way (no tech skills needed):
1. Go to the page where the problem happens.
2. Open the error panel:
   • Chrome:  press Ctrl+Shift+J  (Windows)  or  Cmd+Option+J  (Mac)
   • Firefox: press Ctrl+Shift+K  (Windows)  or  Cmd+Option+K  (Mac)
   • Safari:  press Cmd+Option+C  (Mac)
3. Do the thing that breaks (click the button, reload the page, etc.).
4. Take a screenshot of the panel that just opened — include any RED lines.
5. Reply to this email with the screenshot. That's it!

Even easier: record your screen with the free Clipy Chrome extension and
send us the single link — it captures the errors for us automatically.

Thanks so much — this makes the fix much faster on our end.

Adjust the tone to your brand, but keep the numbered steps and the red-lines detail — that's what saves the second round-trip.

FAQ

What is a console log, in plain English? It's the browser's private notepad where a website records what it's doing while it runs. When something breaks, it usually writes a red error line explaining why. Developers read these lines to find the cause of a bug you're only seeing the symptom of.

How do I open the browser console without any technical skills? Press one keyboard shortcut: Ctrl+Shift+J in Chrome (or Cmd+Option+J on Mac), Ctrl+Shift+K in Firefox, or Cmd+Option+C in Safari after turning on its Develop menu. A panel opens — that's the console. You don't have to understand it, just copy or screenshot it.

Should I copy the text or send a screenshot? Either works. Copy-paste (or a saved .txt/.log file) is better because developers can search it. A screenshot is safer if you're not sure which lines to select — just capture the whole console panel, including the red errors and the page URL.

How do I send console errors to a developer if I'm on my phone? Phone browsers don't let you open the console directly. Record your screen while the bug happens instead and share that. On iPhone use the built-in Screen Recording, or use a screen recorder that captures the error report for you so the developer gets everything in one link.

Is there a way to skip opening the console entirely? Yes — record your screen with a tool that captures the console for you, then send the single link. That removes the hardest part (knowing which console lines matter) and gives the developer the video and the errors together.