Quick answer
This Bottom text processing runs locally and does not upload; browser extensions can still read the page. Bottom text delivers the turn/punchline and is often shorter than the top.
Why it matters
Local processing reduces upload risk but is not absolute security.
Put the punch word on the last line.
Step by step
- Confirm the use/platform size; don't grab random web images.
- Pick a 1:1 or platform ratio and keep text to 2-3 lines.
- Use a high-contrast outline so it reads on a phone.
- Export PNG and check text/faces/edges.
- Confirm image/likeness rights before publishing.
Common mistakes
- Text too long to read on a phone.
- White text without an outline disappears on bright backgrounds.
- Using unlicensed images/people for commercial content.
- Cropping a watermark/logo and publishing anyway.
Checklist
- Size/ratio match the platform.
- Text is 2-3 lines with a clear outline.
- Image/likeness rights are cleared.
- No watermark/private data.
- Export PNG and spot-check.
Key facts
- Put the punch word on the last line.
- Keep bottom text off the very edge.
FAQ
Does Bottom text processing upload my files?
This Bottom text processing runs locally and does not upload; browser extensions can still read the page. Bottom text delivers the turn/punchline and is often shorter than the top.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: Wikipedia image macro