# Report an Issue & Get Support > How to report a bug so we can actually fix it, where to request features, and what to try first when something in Darkroom isn't behaving. Source: https://darkroom.co/help/app/report-an-issue Section: App Updated: 2026-09-08 There are three different things people usually mean by "support," and they go to three different places. A **bug** — something broken, crashing, or rendering wrong — should go through **Report an Issue** inside the app, because that's the only route that carries the diagnostic information we need. A **feature request** belongs on the [suggestion board](https://darkroom.nolt.io), where you can also vote on what others have asked for. And a **question** about how something works is usually answered faster right here in the help center or by [emailing us](mailto:feedback@darkroom.co). ## Reporting a bug **Report an Issue** lives in the **•••** action menu. It submits directly from the app — there's no email client involved and nothing to copy and paste — and it attaches the diagnostic logs from your session automatically. Those logs are the whole point. A description tells us what you saw; the logs tell us what the app was actually doing at the time, which device and OS you're on, which build you're running, and where things went wrong internally. That difference is frequently what separates a bug we can fix this week from one we can't reproduce at all. If you take one thing from this page: report from inside the app rather than describing the problem to us from the outside. You can include your **email address** when you report, and it's worth doing. Most reports don't need a follow-up, but the ones that do are usually the interesting ones — we may need one more detail, or want to send you a build to confirm a fix. Without an address, a report is one-way. ### Making a report more useful A few things sharpen a report considerably: - **Steps to reproduce.** What you did, in order, immediately before it went wrong. "Crashes on export" is hard to act on; "crashes when exporting a RAW with a subject mask and a frame applied" is often enough on its own. - **How often it happens.** Every time, or once? A reliable reproduction is far easier to chase than an intermittent one, and knowing which it is changes how we look. - **A screenshot or screen recording.** Essential for anything visual — a rendering artifact, a misplaced control, a layout issue. A recording is better still for something that only appears mid-gesture. - **The specific photo, if it's photo-specific.** Some bugs only occur with a particular format, capture source, or edit combination. ### Before you report Two quick checks resolve a good share of problems and save you the wait: **Update Darkroom and your OS.** A lot of what gets reported is already fixed in a newer build — check the [update history](/updates) to see whether your symptom is listed. Many rendering and export issues in particular were addressed across the 7.0 and 7.1 releases. **Try the caches.** In [Settings](/help/app/settings), **Clear Photo Cache** resolves stale or wrong-looking thumbnails, and **Clear Sync Cache** resolves [presets](/help/edit/presets) that aren't syncing correctly between devices. Neither touches your actual photos — your originals live in iCloud Photos and aren't affected. ## Requesting a feature Feature requests go to our public [suggestion board](https://darkroom.nolt.io). Posting there rather than emailing is genuinely better for you: requests are public, you can see whether something has already been asked for, and you can vote — which is a real input into what we build next. If a capability isn't in the app today, the board is also the fastest way to find out whether it's already on our radar. ## Getting help with a membership Billing, refunds, restores, and Family Sharing questions have their own page — start with [Darkroom+ Membership](/help/membership/darkroom+), which covers the common cases including "I paid but don't have access." Apple is the merchant of record for all App Store purchases, so refunds and cancelations ultimately go through your Apple account rather than through us. ## Frequently Asked Questions ### How do I report a bug or crash? Use **Report an Issue** in the *•••* action menu inside Darkroom. It submits directly from the app with diagnostic logs attached, which is far more useful to us than a description alone. Add your email address if you're happy for us to follow up. ### Why report in the app instead of emailing? Because the in-app report carries the diagnostic logs from your session — your device, OS, build number, and what the app was doing when it went wrong. Emailed descriptions frequently can't be reproduced, and that's usually the difference between a bug getting fixed and not. ### Will you reply to my report? Not always — most reports don't need a conversation, and the log alone is often enough. Include your email address and we'll reach out if we need another detail or want you to confirm a fix. ### How do I request a feature? Use the public [suggestion board](https://darkroom.nolt.io). You can check whether it's already been requested, add your own, and vote on others — which feeds into what we prioritize. ### Where do I find my build number? At the bottom of [Settings](/help/app/settings). In-app reports include it automatically, so you only need it when writing to us by email. ### Can I just email you? Yes — [feedback@darkroom.co](mailto:feedback@darkroom.co). It's the right channel for questions, membership problems, and anything that doesn't fit a bug report. For an actual bug, please still use Report an Issue so we get the logs. ## Related - [Settings](/help/app/settings) — caches, build number, and app preferences - [Darkroom+ Membership](/help/membership/darkroom+) — billing, restores, and access problems - [Update History](/updates) — check whether your issue is already fixed