Screenshots of Your Own Dashboard, Used Carefully

A screenshot is the cheapest proof you own, and the easiest way to leak a guest name. Four rules make it usable.

Last updated: October 30, 2026

A dashboard screenshot is the fastest way to show someone your occupancy without handing over access to your account. It's also the fastest way to publish a guest's name, a booking reference and a rate you'd rather not have quoted back at you. The difference between the two outcomes is four habits, and none of them takes more than a minute.

Key Takeaways

• A screenshot proves a number appeared, not what it means. The period and the source have to travel with it.
• Mask before you crop. Cropping hides the edges you noticed. Masking covers the fields you didn't.
• Caption the number, not the screen. "Occupancy, October, all four channels" beats a picture with no words.
• Sometimes a table is the better object. Trends, comparisons and anything a reader needs to check belong in text.
• Keep the original, share the copy. One unmarked file in a dated folder saves an argument later.

What a screenshot proves

It proves that at the moment you pressed the keys, a screen in your account displayed a particular figure. That's it. It doesn't prove how the figure was calculated, which bookings were included, or whether the period was a calendar month or the last thirty days.

That sounds like a small point until you're in a conversation where it matters. An owner asking why the flat earned less this quarter, a partner asking how the year is tracking, a lender asking for evidence of trading. In each of those, the number on its own invites a follow-up question, and the follow-up is usually about the period.

So treat a screenshot as one layer of a claim rather than the claim itself. The number, the period, the source and the date you took it are four pieces. A picture carries the first. You have to add the other three in words, and if you can't, the picture isn't ready to send.

There's a second limit worth naming. A screenshot shows a total, and totals hide composition. Two months with the same occupancy can be built from completely different bookings: one long stay, or eleven short ones with eleven changeovers. If the composition is the point, say so. The image won't.

Blurring before you crop

The order here is not a style preference. Crop first and you'll frame the shot around the numbers you wanted, then forget that the guest's name was in the corner you left in because it looked tidy. Mask first and the edges stop mattering.

Start with the fields that identify a person: guest name, phone number, email, booking reference, and any message preview that runs across the top of a screen. Then the fields that identify a commercial relationship: the rate you negotiated with one client, the net payout, the name of an owner who isn't the audience.

Then crop. Cropping after masking is a framing decision, not a privacy one, so you can be generous with it: leave enough context that the reader can see this is your reports page and not a spreadsheet someone typed.

Inside the product, guest details are masked automatically, so what the system surfaces in a shared view carries the booking without carrying the person. A screenshot steps outside that. Once the image leaves the account, nothing is masking anything, and the file gets forwarded, saved to a phone, and re-posted in a group chat where you're not present.

That's the honest way to think about it: the product protects the view, you protect the file. localsbnb.com shows occupancy, ADR and RevPAR with the period attached, so the numbers you're citing arrive with their own context, and the part you have to handle is what sits around them.

Captioning the number, not the screen

A caption that says "our dashboard" tells the reader nothing they can't see. A caption that says "Occupancy 74%, October 2026, Airbnb and Booking.com only" does three jobs at once: it names the measure, the period and the scope.

Scope is the part people skip, and it's the part that causes trouble. If the screenshot covers two channels and the reader assumes four, the number is doing work it can't support. Write the channels in. Write the property in, especially if you run several. Write the date you took the shot, because a report regenerates and a picture doesn't.

Keep the caption short enough to read on a phone. One line for the measure and period, one line for scope, and a third only if there's something a reader would otherwise misread. Then put the full file name and date in the document's notes, not in the caption.

If you're reusing the same screenshot in a deck and in an email, resist the urge to write two different captions. Pick one, and keep the wording identical across both. The moment a number gets described two ways, someone will ask which description is right, and the answer will be "neither, it was a rough count".

One quick test. Cover the caption with your thumb and look at the image. If you can't tell the period from what's left, the caption isn't finished.

When a screenshot is the wrong choice

Three situations where a picture weakens the argument.

The first is a trend. A single frame can't show direction, and a gallery of five frames asks the reader to do arithmetic. A four-row table with the period in the first column does the job in less space and survives being copied into an email.

The second is anything a reader needs to check. If the point is that a figure is defensible, the reader wants the method: which bookings, which period, whether cancellations were excluded. That's a sentence or two of text, and no image can hold it.

The third is a number that's still moving. Provisional figures, a month that hasn't closed, a channel whose sync is behind. Sharing a screenshot of a number you'll have to revise is worse than sharing nothing, because the revision has to be explained later and the explanation sounds like an excuse.

When in doubt, ask what the reader will do with the image. If the answer is "look at it and take my word", a screenshot is fine. If the answer is "check it, compare it, or forward it to someone who will", write it down instead.

None of this means don't share numbers. It means share them in the object that survives being forwarded, which is usually text.

FAQ

Can I post a screenshot of my own dashboard publicly?

You can, and it's your account, but check three things first. Whether the image shows a guest, whether it shows a rate or a payout you agreed to keep private, and whether the period is stated. Public posts get screenshotted again, and the second copy rarely carries your caption.

Is a screenshot enough for an owner or a lender?

Sometimes as a supporting item, rarely as the only one. The figure needs a period attached, and the person reading it usually wants to know how it was produced. Ask what they need before you send a picture, because the answer is often a short statement rather than an image.

What if the numbers look worse than last month?

Say so, and say why in one line. A screenshot with no explanation invites the reader to invent one, and the invented one is usually about the host rather than the season. Composition, a long booking ending, a channel that was paused: all of those are visible in a sentence.

The rule underneath all four habits is simple. A screenshot is a copy of a moment, and the moment needs a label. localsbnb.com keeps occupancy, ADR and RevPAR on the same reports page with the period in view, which makes the label easy to write and the crop easy to keep tight.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Privacy and data-protection duties for guest information, and what you may publish about a property or a tenancy, are set by local law and by each platform's terms. Confirm the current requirements with the competent authority and the current terms of each platform you use before you act.