Contact

Contact

Email: everydayroyalties@gmail.com

How to Reach Us

Email: everydayroyalties@gmail.com

Response Times

We aim to reply within a few business days, though response times can vary with volume. For time‑sensitive notes, include ‘Urgent’ in the subject line.

Accessibility & Alternate Formats

If you use assistive technology and encounter a barrier, email a short description of the step that failed, your device/browser, and any screenshots. We’ll prioritize a fix and can provide content in alternate formats upon request.

Feedback That Helps

  • The tool page and action you took (e.g., ‘Resize → 1200px’).
  • Your source image type and target format.
  • What you expected vs. what happened (with screenshots if possible).

Updated Oct 01, 2025

Support Channels

What We Can Help With Quickly

  • Troubleshooting an image that won’t load or export.
  • Clarifying which settings to use for a target platform.
  • Bug reports with reproducible steps.

What Takes Longer

  • Feature requests (we’ll add to the roadmap and circle back).
  • Investigation of rare device/browser combos.

Helpful Report Template

Copy/paste this and fill in the blanks for the fastest resolution:

Tool used: (Compress / Resize / Convert / Rotate/Flip)
Source format & size: (e.g., PNG 3000x2000, 3.1 MB)
Target settings: (e.g., WEBP Q80, 1200px longest side)
Device & browser: (e.g., iPhone 14, Safari 17)
Steps to reproduce: (1) ... (2) ... (3) ...
What you expected:
What happened instead:
Screenshots (if any):

Response Time & Follow‑Up

  • We try to reply within a few business days.
  • If your note is urgent, include “Urgent” in the subject and why.

Updated Oct 01, 2025

Getting help effectively

Providing details helps diagnose tool behavior quickly.

Include the tool used, file type, and expected result.

Page-specific details

Support moves fastest when you describe what you expected versus what you got. Example: “Converted PNG to JPG and the background turned black” or “Compressed at 60% and text became blurry.”

If possible, include the original dimensions and the export settings you selected so the issue can be reproduced.

Troubleshooting tips before you reach out

Most “unexpected results” fall into a few categories: wrong dimensions, quality too low, transparency lost, or orientation changed after export. Knowing which category you are in helps pinpoint the fix quickly.

When you report an issue, describe the destination. “This needs to be accepted by Instagram” or “This is for a Shopify product grid” gives a clearer target than “it looks wrong.”

If a file won’t upload, mention the file size in MB and the output format you chose.

Quick checklist

Examples

ProblemLikely causeBest next step
Background turned solidTransparency not supportedExport as PNG/WebP
Text became fuzzyQuality too lowIncrease quality slightly
Image looks stretchedAspect ratio mismatchMaintain ratio or crop

Examples of issues and the likely fix

Most problems have a straightforward cause once you match them to the right tool setting. The examples below help you troubleshoot without guessing.

If you still need help, include the destination (Instagram, Shopify, email, CMS) because each platform recompresses differently.

Useful details that speed up support

The fastest fix usually comes from knowing the destination and the image type. A photo behaves differently than a logo, and a Shopify upload behaves differently than a Gmail attachment.

If you’re reporting a quality issue, mention where you noticed it: on the exported file, or only after uploading to another site. That tells us whether the problem is the export or the platform’s reprocessing.

Include these when possible

What “quality issue” usually means

Quality complaints typically fall into one of these buckets: the image was resized too small, the compression quality was too low, or the platform recompressed the upload after the export.

To pinpoint it, compare the exported file on your device versus the same file after upload. If the export looks great locally but bad online, the platform is likely doing extra processing.

Helpful comparison steps

Fast troubleshooting map

If something goes wrong, it helps to identify whether the problem is coming from the export step or from the platform where you uploaded the file. Use the checkpoints below to narrow it down quickly.

If you send a message, include the exact page you used (Resize/Compress/Convert/Rotate) and what the destination is (Shopify, Instagram, Gmail, etc.). That single detail usually makes the fix obvious.

For photographers: common delivery questions

If you’re delivering a set to a client, the usual constraints are file limits (portals/email) and consistency across the set. If you tell us the destination (Pixieset, Google Drive, email, website CMS), we can recommend the safest export approach.

Common “why did it get bigger?” explanation

Sometimes a file grows after conversion because the new format is less efficient for that kind of image. Screenshots and graphics can expand when moved to photo-focused formats; photos can expand when moved to lossless formats. The fix is to choose the format that matches the content type.

What to report when something looks wrong

If a result looks bad, the fastest diagnosis is comparing the exported file to the version after upload. That single comparison tells you whether the export settings or the destination platform caused the issue.

Include these details

Bonus: mention whether the problem is blur, color shift, halos, or rejection—each points to a specific fix.

Fast self-check before asking for help

Before troubleshooting, run this quick self-check. It catches most problems without needing extra steps.

If the export is perfect locally but ugly after upload, your destination platform is reprocessing it—optimize to survive that reprocessing.

Changelog

This section has been tailored for this page to avoid duplication while preserving intent.