Best for
App logs, CLI output, crash reports, and build logs that need another set of eyes.
Share a log file without the email mess
Send logs as a quick file share or paste text directly when the output fits better in plain text.
For many debugging cases, the fastest path is a short-lived log share. Upload the file or paste the text and send the link to the person helping.
Debugging
What you need to know
For many debugging cases, the fastest path is a short-lived log share. Upload the file or paste the text and send the link to the person helping.
Why it works
You can choose text or file based on what makes the output easiest to inspect.
What to know
Remove secrets before sharing. The service does not inspect or redact your content.
Size limit
Very large log bundles over 25 MB need a different delivery path.
More detail
Text share or file share for logs
Small logs are often easier to share as text because the recipient can read them right in the browser. Larger or multi-file outputs usually work better as a file upload.
Either way, the value is the same: short setup, short link, and an access window that keeps the debugging artifact from living forever.
How it works
How to share a log file
Paste readable output or upload a log file, then send the short link.
-
Step 1
Choose text for readable output or file for packaged logs.
-
Step 2
Set the access window based on how long the debugging round will last.
-
Step 3
Send the link to the person helping with the issue.
FAQ
Page-specific questions
These answers match the use case on this page and the actual product limits.
Should I paste logs or upload them as a file?
Paste them when the content is readable as plain text. Upload a file when formatting or packaging matters.
Does the service scan logs for secrets?
No. Review the content yourself before sharing.
Keep exploring
Related pages
If this page is close to what you need, these are the next links worth opening.