DEV Community: wendygostudio

Stop uploading your screenshots to resize them

wendygostudio — Mon, 29 Jun 2026 14:54:15 +0000

Every time you resize a thumbnail, you face a choice: upload it to Canva (or similar), or resize it locally. Most creators default to uploading without thinking about what that means.

If you're publishing frequently — multiple videos a week, social posts, platform-specific sizes — you're sending a lot of images to third-party servers. Not because you have to, but because the tool you grabbed doesn't offer an alternative.

The Upload Problem

Canva is excellent at what it does: full-featured design from scratch. You add text, backgrounds, icons, brands. That power justifies the cloud requirement. But for the "I have a screenshot and need it at exactly 1200×627 for LinkedIn" task, you're paying a cost you might not need to:

Time: Open Canva → create design → upload image → position → download
Privacy: Your image lives on Canva's servers for the duration
Account burden: One more login to maintain

If you already have the image, uploading it to resize is friction.

The Local-First Alternative

FrameForge works the opposite way. Open the extension, select your image, pick a platform preset (YouTube, Instagram, LinkedIn, X — dimensions lock automatically), adjust the crop, and export. No account. No upload. No internet needed after install.

The step count is half. The image never leaves your machine. And it takes the same 30 seconds whether you're resizing for the first time or the hundredth.

The real difference is the starting assumption. Canva assumes you're designing. FrameForge assumes you already have the image.

When Privacy Actually Matters

For personal projects, uploading a screenshot might feel harmless. But if you're:

Working with client assets before they're public
Resizing screenshots of unreleased products
Publishing drafts that aren't ready to share with the world
Building in restricted environments where file uploads trigger security reviews

...then uploading each thumbnail becomes a problem. Not because the platform is untrustworthy, but because architectural constraints matter.

FrameForge processes everything in your browser. Your files stay on your machine.

The Honest Take

Canva and FrameForge solve different problems. Many creators use both:

Canva for designed thumbnails where the layout is the work (text, brand colors, composed elements)
FrameForge for quick adaptation (you have the image, you need specific dimensions)

But if you're in the second camp — "I publish frequently and just need to resize" — you might be using a sledgehammer for a nail.

📖 Read the full guide with more details on wendygostudio.com

Stop Sorting Lists by Hand: A Browser Extension That Does It in One Click

wendygostudio — Sun, 28 Jun 2026 11:37:35 +0000

The Sorting List Bottleneck

You pull a list of hostnames from your monitoring dashboard. A dependencies export from your package manager. Error codes from logs. Config keys from an env dump. And every single time, they come out in insertion order — not alphabetical.

So what do you do?

Most developers reach for Excel or Google Sheets: paste, click Data > Sort, copy back. Others open the terminal, save to a file, run sort, capture the output. Some paste into a random online sorter and hope their internal hostnames don't end up in someone's database.

All three options suck for the same reason: friction.

The task is trivial — alphabetize a list. But the ceremony around it isn't.

Why This Matters More Than It Sounds

Sorted lists aren't just neat. They're:

Faster to scan: Configs, dependency lists, and server inventories are easier to audit when entries cluster together alphabetically
Cleaner diffs: When you sort before committing, reviewers see what was added/removed, not a jumbled re-order
Less error-prone: Manual eye-sorting over 10+ items is a recipe for transpositions you'll catch at 3am

The One-Click Alternative

A browser extension that sorts text locally in your browser changes this completely. No copy-paste shuffling. No file saves. No terminal flags to remember. One click from your toolbar, and your list is sorted — without leaving your browser.

The beauty is that everything stays local. Your server hostnames, API paths, or sensitive config keys never touch an external server. It's just you, your browser, and your list.

A Real Example

Say you pull this server inventory from a dashboard:

Paste it in, apply the sort, and instantly get:

Six hostnames sorted in under two seconds. Ready to paste into your runbook, your Terraform config, or your code review.

The Browser Extension Wins

Beyond sorting, a good extension can also extract emails, URLs, and IPs from mixed text — pull them all from a log file without regex. Encode/decode Base64 for JWT inspection. Generate UUIDs on the fly. All free, all local, all one click away.

This is the kind of tool that saves 30 seconds here, a minute there — but over a year, it compounds into actual time back in your life.

The Bottom Line

If you manage lists, hostnames, configs, or logs as part of your workflow, try sorting with a browser extension instead of the next manual method. You might be surprised how much friction disappears.

📖 Read the full guide with more details on wendygostudio.com

Why X is Cropping Your Tweet Images (And How to Fix It)

wendygostudio — Sat, 27 Jun 2026 10:31:22 +0000

Your carefully chosen tweet image just went live—and it looks like it got decimated in the X feed preview. The top and bottom are missing. Portrait shots are squeezed into a weird vertical strip.

If this sounds familiar, X is doing what it's designed to do: center-crop your image to a 2:1 aspect ratio in the timeline feed. It's not a bug. It's the platform's image rendering behavior, and once you know the target dimensions, it's trivial to work around.

The Crop Problem

X applies a center-crop to inline images in the feed. A square photo (1:1) becomes a 2:1 slice—goodbye top quarter, goodbye bottom quarter. Portrait images (9:16, the default from most phone cameras) get hit even harder: roughly 80% of the vertical height disappears in the feed preview alone.

So your carefully framed smartphone photo or custom graphic gets butchered before most people even click to expand it.

The One-Size Solution

Post at 1200×675 px (16:9 aspect ratio) and none of this happens.

Why? Because 1200×675 is already 16:9. When X's 2:1 feed preview tries to crop it, there's no excess to remove—the image already fills the exact space. You get no surprise cropping in the feed, and the full image displays without letter-boxing or awkward padding when someone expands it.

This is the same 16:9 ratio used by YouTube thumbnails (1280×720), so if you cross-post video previews to both platforms, the composition stays consistent.

How to Resize Without Breaking Your Workflow

If you're doing this manually with PIL, ImageMagick, or desktop software, it works—but you're stuck uploading files, opening tools, waiting for batch processing.

FrameForge is a Chrome extension that does this in-browser with no upload, no account, no server. You get platform presets (X Post, YouTube, Instagram, Twitch) that lock the canvas to the right dimensions. Drag your crop overlay to frame what matters. Export. Done.

For developers, the appeal is obvious: resize once per platform, export each variant in seconds, move on. No switching tools. No waiting for external services. Image processing stays local.

The Multi-Platform Angle

If you're the type who posts the same content to Twitter, YouTube thumbnails, and Instagram in one sitting, FrameForge handles all three presets from one extension. Set your source image, select the platform, crop once, export. Repeat for the next platform. It's faster than uploading to three different online tools.

Quick Takeaway

Post X images at 1200×675 px and the 2:1 feed crop won't steal your content. If you're doing this repeatedly, automate it: FrameForge, command-line tools, or whatever fits your workflow. Just stop letting the platform's default center-crop drive the design.

📖 Read the full guide with more details on wendygostudio.com

Stop Pasting Your Contact Data Into Random Websites

wendygostudio — Fri, 26 Jun 2026 12:34:51 +0000

Stop Pasting Your Contact Data Into Random Websites

You've all been there: a forwarded email chain with contact information scattered everywhere, a CRM export that's one giant mess, or a log file where email addresses are buried in timestamps and server IPs.

Your first instinct? Fire up Google, find an "email extractor" website, paste your text, and hope nobody is logging what you just sent.

But here's the thing: why are you uploading contact data to a third-party server when you don't have to?

The Privacy Problem With Online Extractors

Online email extraction tools are convenient, sure. But they require uploading your data to someone else's server. If you're extracting contact lists from a CRM, customer emails, internal team rosters, or log files with sensitive information, you're creating a data handling risk.

Sure, they probably aren't storing anything. Probably. But why take the chance?

A Better Approach: Local Extraction in Your Browser

What if you could extract emails in seconds, entirely in your browser, without uploading anything? That's exactly what TextForge does. It's a free Chrome extension that pulls email addresses from any text block, locally, on your machine.

No servers involved. No data in transit. No terms of service you didn't read.

How It Works (5 Simple Steps)

Install TextForge — Grab it from the Chrome Web Store, pin it to your toolbar
Click the extension — Opens instantly in a side panel
Paste your text — Drop in your log file, email export, document text, whatever
Select "Extract Emails" — TextForge scans the input and pulls out every email address
Copy and go — Instant results, copy to your clipboard, done

Real Example

Say you get a chunk of contact text like this:

Our event contacts: Alice Mora (alice.mora@example.com), facilities coordinator; 
Robert Kim <r.kim@venue-partners.org>; billing enquiries to billing@acme-ltd.co.uk. 
CC the team at events@example.com for all confirmations.

Hit "Extract Emails" in TextForge and you get:

alice.mora@example.com
r.kim@venue-partners.org
billing@acme-ltd.co.uk
events@example.com

Four addresses, instantly, from a paragraph of mixed text. No regex patterns to remember, no copy-paste hunting.

Why This Actually Matters

Speed: No server round trip, no loading spinner waiting for a response.

Privacy: Literally nothing leaves your machine. Processing happens entirely in your browser.

Simplicity: One click from your toolbar. No opening a new tab, no "accept our cookies" modal, no account signup.

TextForge also handles extraction for URLs and IP addresses — useful if you're parsing logs where multiple data types are mixed together.

The free version includes all extraction functions. No account needed, no premium upsell.

📖 Read the full guide with more details on wendygostudio.com/blog/extract-emails-from-text/