# ConverterUp

> Free online file converter for images, video and audio — MP4, MP3, HEIC, PNG, JPG, WebP and more. Runs 100% in your browser: no upload, no signup, no limits.

ConverterUp is a free collection of 25 browser-based converters and utilities. Every file is processed locally with WebAssembly (FFmpeg.wasm, libheif) and standard browser APIs — nothing is uploaded, there is no account, no daily limit and no watermark. The site is funded by ads and available in English, Portuguese (/pt) and Spanish (/es).

## Key facts

- Price: free, unlimited. No paid plan, no sign-up.
- Privacy: files never leave the user's device; conversion runs client-side.
- Limits: 500 MB per video, 50 MB per image (browser memory).
- Image formats: PNG, JPG, WebP, AVIF, GIF, TIFF, BMP, HEIC/HEIF, SVG, ICO.
- Video formats: MP4, WebM, MOV, MKV, AVI, FLV, 3GP, TS, M4V, WMV; video to GIF; audio extraction to MP3, AAC, WAV, OGG.
- Languages: English, Portuguese, Spanish.

## Tools in detail

### Video Converter — Convert Video to MP3, MP4 & More

URL: https://converterup.com/tools/media-converter

ConverterUp's media converter changes the format of videos and images directly in your browser. Turn an iPhone MOV into an MP4 that plays everywhere, shrink a screen recording to WebM for the web, rescue an old FLV or WMV clip, convert a PNG to JPG or WebP, or pull the soundtrack out of a video as MP3. It runs FFmpeg compiled to WebAssembly on your own device, so nothing is uploaded, there is no queue, and private footage stays private.

#### Which video format should you pick?

MP4 (H.264 + AAC) is the safe default. It plays on every phone, TV, browser, social network and editing app. If you are not sure what the recipient uses, choose MP4.

WebM (VP8/VP9 + Vorbis/Opus) is the open web format. It is royalty-free and usually smaller than MP4 at similar quality, which makes it a good choice for videos embedded on your own website. Older Apple software has patchy support, so avoid it for files you send to iPhone users.

MKV is a flexible container that can hold several audio tracks and subtitles. It is ideal for archiving, but many phones and TVs will not play it — convert MKV to MP4 before sharing. MOV is Apple's container (what iPhones record); AVI and WMV are legacy Windows formats worth converting to MP4 for modern players.

#### Image formats: PNG, JPG, WebP, AVIF and more

JPG is best for photos: small files, universal support, but no transparency. PNG is lossless and supports transparency — use it for screenshots, logos and graphics with sharp edges.

WebP and AVIF are modern web formats. WebP is typically 25–35% smaller than JPG and supports transparency and animation; AVIF goes further still but takes longer to encode. Both are supported by every current browser.

GIF is limited to 256 colours — convert animated GIFs to MP4 or WebM to cut file size by 80–95%. TIFF and BMP are large, uncompressed formats from print and old Windows software; converting them to PNG or JPG makes them shareable. JFIF files are just JPEGs with a different extension and convert to plain .jpg.

#### Audio extraction, quality and limits

Switch on audio extraction to save only the soundtrack of a video as MP3, AAC, WAV or OGG — handy for podcasts, lectures, voice notes and music clips.

The quality slider controls compression: higher keeps more detail and produces bigger files. You can also set a width and height; with the aspect-ratio lock on, the image or video is scaled without distortion.

Because processing happens on your device, speed depends on your CPU and memory. The browser can handle videos up to 500 MB and images up to 50 MB. For larger files, trim or compress them first. Converting video is CPU-heavy — a desktop browser is noticeably faster than a phone.

**Q: Are my files uploaded to a server?**

No. Conversion runs entirely in your browser with FFmpeg compiled to WebAssembly. Your files never leave your device, which also means there is no upload wait.

**Q: Which formats are supported?**

Video input: MP4, MOV, MKV, WebM, AVI, FLV, 3GP, TS, M4V, WMV. Video output: MP4, WebM, MKV, AVI, MOV. Images: PNG, JPG/JPEG/JFIF, WebP, AVIF, GIF, TIFF and BMP in both directions. Animated GIFs can also be converted to MP4 or WebM. Audio extraction: MP3, AAC, WAV, OGG.

**Q: What is the maximum file size?**

500 MB for videos and 50 MB for images. These limits keep the conversion within the memory a browser tab can safely use.

**Q: How do I convert MOV to MP4?**

Drop the MOV file, choose MP4 as the output and click convert. The video is re-encoded to H.264 with AAC audio, the most widely compatible combination.

**Q: Can I extract MP3 from a video?**

Yes. After adding the video, enable audio extraction and choose MP3 (or AAC, WAV, OGG). Only the audio track is saved.

**Q: Is there a daily limit or watermark?**

No. The converter is free with no daily limit, no watermark and no account.

### Compress Image — Reduce Image Size Free, No Upload

URL: https://converterup.com/tools/image-compressor

Compress PNG, JPG, WebP, AVIF and HEIC images directly in your browser without losing visible quality. ConverterUp's image compressor is built for designers, developers, and anyone who needs to reduce image file sizes for faster websites, smaller email attachments, or social media uploads. Set the quality slider to find the right balance between size and clarity, click compress, compare the original and compressed sizes, and download the result. Files never leave your device — the browser's own canvas does the encoding — so the originals stay private and there is no upload queue or wait.

#### JPG, PNG, WebP, AVIF — which format compresses best

JPG is the workhorse for photographs. It uses DCT-based lossy compression that is tuned for natural images with smooth gradients (skin, sky, foliage) and can shrink a 6 MB RAW-export down to 200–400 KB at quality 80 with no visible difference. It is a poor choice for screenshots, logos, or anything with sharp edges and flat colors because ringing artifacts appear around hard transitions.

PNG is lossless and ideal for UI screenshots, icons, line art, and any image that needs a transparent background. Its compression is based on DEFLATE, which works well on large flat areas but cannot exploit the perceptual tricks JPG uses on photos. A 4000 × 3000 photo saved as PNG can be 20× larger than its JPG equivalent at quality 85.

WebP supports both lossy and lossless modes in one container, with transparency in both. Lossy WebP beats JPG by roughly 25–35 % at the same perceptual quality; lossless WebP beats PNG by 20–25 %. It is supported in every modern browser since 2021 and is the safe default for new web assets.

AVIF is newer (AV1 still-frame), produces files 40–50 % smaller than JPG, and supports HDR plus wide gamut. The trade-off is slower encode speed and slightly less compatibility with older email clients and image editors. For hero images, OG cards, and product photos delivered to modern browsers, AVIF wins on size. For email attachments and editor compatibility, stick with JPG or WebP.

#### Quality slider strategy: where the sweet spots live

Most encoders expose a 0–100 quality scale that is non-linear: dropping from 100 to 90 often halves the file size for almost no perceptual loss, while dropping from 50 to 40 barely shrinks the output and introduces visible blockiness. The sweet spot lives between 75 and 85 for almost every photographic use case.

For JPG, quality 80 is the canonical web setting — it is what most CMS pipelines (Cloudinary, imgproxy, Next.js Image) default to. Go to 85 for hero photos and portraits where skin tones matter; drop to 70 for thumbnails and grid views where size matters more than perfect detail.

For WebP, quality 75 produces a file roughly equivalent to JPG quality 85 in perceptual terms, so you can be more aggressive than with JPG. For AVIF, quality 50–60 is comparable to JPG 80 because AVIF's quality scale is calibrated differently. Always preview side-by-side at 100 % zoom before locking a quality for a batch.

If you serve responsive images, compress each size with the quality budget appropriate to its viewing distance. A 320-pixel-wide thumbnail tolerates quality 60 because no one inspects it closely; a 2560-pixel-wide hero on a 4K monitor needs quality 85+ to avoid visible chroma noise.

#### Lossless vs lossy: when to choose which

Lossy compression discards perceptual information that the human eye cannot easily recover — high-frequency detail, subtle color variation, fine noise. It is irreversible: once you save at quality 70, the information is gone, and re-saving at quality 100 will not restore it. Use lossy for any photograph delivered to end users.

Lossless compression rearranges bytes so the file is smaller but the pixels are bit-for-bit identical when decoded. Use lossless for source masters you will re-edit, for screenshots of text and UI where every pixel matters, for charts and diagrams with sharp lines, and for any image that will be re-encoded multiple times in a pipeline (each lossy re-save compounds artifacts).

A common workflow mistake is treating every image the same. Keep a lossless master (PNG or WebP-lossless), then export lossy delivery copies (JPG/WebP/AVIF) sized for each use case. That way you can always re-export at a different size or quality from the master without generation loss.

**Q: How much can I compress an image without visible quality loss?**

JPG and WebP usually compress to 60-80 % quality with no visible difference for photographs. PNG benefits less from quality changes because it is lossless. Convert to WebP or JPG for the largest savings.

**Q: Is there a file size limit?**

There is no fixed size limit — the practical ceiling is your device's memory. Most modern phones and laptops handle 20–30 MB photos without issues; very large images may be slow on older phones.

**Q: Are my images uploaded to a server?**

No. Compression happens entirely inside your browser using its built-in canvas encoder (HEIC files are decoded locally with WebAssembly first). The image bytes never leave your device, and ConverterUp has no upload endpoint at all.

**Q: Which formats are supported?**

Input: PNG, JPG/JPEG, WebP, AVIF and HEIC/HEIF. The compressed file keeps a compatible format: PNG stays PNG, JPG stays JPG, WebP stays WebP, AVIF is saved as WebP and HEIC as JPG. To change format on purpose, use the Media Converter.

**Q: Does compressing an already-compressed JPG help?**

Marginally, and at a cost. Re-encoding a lossy JPG always introduces additional generation loss, even at quality 100, because the decoder must round to integer pixels before the next encode. Lower the dimensions or convert to WebP/AVIF instead — both yield a real size reduction without stacking JPG artifacts.

**Q: Is EXIF metadata kept after compression?**

No. The compressor re-encodes the pixels through the browser canvas, which drops EXIF metadata such as GPS coordinates, camera serial numbers and timestamps. That is usually what you want before sharing; if you need to keep metadata, keep a copy of the original file.

### Resize Image Online Free — Exact Pixels, No Upload

URL: https://converterup.com/tools/image-resizer

Resize images online to exact pixel dimensions or by percentage, with optional aspect ratio lock to prevent distortion. ConverterUp's image resizer is useful for preparing photos for blog posts, e-commerce listings, profile pictures, or printable assets that require a specific size. Drop a PNG, JPG, WebP, or AVIF file, type your target width and height, and download the result in seconds. The resizing runs entirely in your browser, so original photos and any sensitive content never leave your device or get queued on a remote server.

#### Target sizes for social, web, and print

Open Graph / Twitter cards: 1200 × 630 is the universal safe size for link previews on LinkedIn, Facebook, Twitter/X, Slack, and Discord. Slack still crops at 1200 × 627, so keep critical content inside a centered 1200 × 600 safe area.

Instagram: feed posts 1080 × 1080 square or 1080 × 1350 portrait; Stories and Reels 1080 × 1920 (9:16). YouTube thumbnails: 1280 × 720. TikTok: 1080 × 1920. LinkedIn cover: 1584 × 396.

Web favicons: ship a 32 × 32, 180 × 180 (Apple touch), and 512 × 512 (PWA) at minimum. For retina displays, export at 2× the CSS pixel dimensions and let the browser downscale — a button that displays at 200 × 50 CSS pixels should be a 400 × 100 image.

Print: photographic print at 300 DPI means an A4 page needs roughly 2480 × 3508 pixels; a 6 × 4 inch postcard needs 1800 × 1200. For posters viewed from a distance, 150 DPI is acceptable. Always export print masters as PNG or TIFF, not JPG.

#### Aspect ratio, cropping, and content-aware fits

When the target dimensions match the source aspect ratio, resizing is a pure scale. When they do not, you must choose: letterbox (preserve the whole image, add padding), crop (preserve the aspect ratio, trim edges), or stretch (distort the image to fit). Stretching is almost always wrong unless you are creating an intentional effect.

For portraits and product shots where the subject is centered, a simple center crop works. For landscapes and group photos, a center crop often cuts off important content — pre-crop in an image editor before resizing. ConverterUp's resizer scales the whole image and never crops.

The aspect ratio lock in the resizer prevents accidental distortion: change one dimension and the other follows. Turn it off only when you genuinely want to squash or stretch (rare), and verify with the live preview that the result still reads correctly.

For e-commerce catalogs, decide on a single canonical aspect ratio (4:5 portrait is popular) and crop every product photo to that ratio before resizing. Inconsistent aspect ratios across a grid look amateurish and break responsive layouts.

#### Resampling algorithms and quality

When you change pixel dimensions, every output pixel has to be reconstructed from multiple input pixels. The reconstruction algorithm dictates how sharp or how soft the result looks. Nearest neighbor picks the closest source pixel — fast, but produces jagged edges. Use it for pixel art and never for photos.

Bilinear averages 4 surrounding pixels — smooth but a bit soft. Bicubic uses 16 pixels with a cubic weighting — the default for most image editors and the right choice for general photo work. Lanczos (sinc-based) uses 36–64 pixels and produces the sharpest results, especially for large downscales, at a small CPU cost.

ConverterUp resizes with the browser's high-quality image smoothing, which produces clean, sharp downscales in every modern browser. After downscaling a photo by more than 4×, applying a mild unsharp mask in your editor restores the perceived sharpness that is naturally lost in any resampling step.

**Q: How does aspect ratio lock work?**

When the lock icon is active, changing width updates height proportionally and vice versa, preserving the original aspect ratio. Disable it when you intentionally want to stretch or squash the image to non-proportional dimensions.

**Q: What is the maximum image size I can resize?**

There is no fixed size limit — the practical ceiling is your device's memory. Very high-resolution images (above 8000 pixels on either side) may be slow on low-end mobile devices because resampling runs on the CPU.

**Q: Will my image lose quality when resized?**

Downscaling is lossy by nature, but ConverterUp uses the browser's high-quality resampling to keep the result sharp. Upscaling cannot add detail that isn't there, so increase dimensions only when strictly needed.

**Q: Which formats are supported?**

Input: PNG, JPG/JPEG, WebP, GIF and AVIF. The resized image keeps the original format when your browser can encode it (PNG, JPG and WebP everywhere); otherwise it is saved as PNG. Animated GIFs are resized as a single still frame.

**Q: Can I resize by percentage instead of pixels?**

Yes, for the common cases: the 50% and 25% buttons scale both sides in one click. For any other size, type the exact width or height in pixels — with the aspect-ratio lock on, the other side follows automatically. Presets for 1920 × 1080, 1280 × 720, 800 × 600 and 640 × 480 are also available.

**Q: Why does my upscaled image look blurry?**

Resampling cannot invent detail that was never captured. Bicubic and Lanczos interpolate between existing pixels but cannot recover edges that were never sampled. For genuine upscaling (e.g., 2×) you need an AI super-resolution model; for the resizer, treat upscaling as a last resort and prefer requesting a higher-resolution source.

### Video to GIF Converter — MP4, MOV, WebM Online

URL: https://converterup.com/tools/video-to-gif

Convert video to GIF online from MP4, WebM, MOV, AVI, MKV and more without uploading anything. ConverterUp's video to GIF tool is ideal for creating short loops for documentation, product demos, social media reactions, and chat platforms like WhatsApp, Slack, or Discord. Choose a frame rate and width, convert, and download the animated GIF directly to your device. Conversion runs in the browser using FFmpeg compiled to WebAssembly, so even private clips and screen recordings stay on your machine. For best results, trim long videos to the few seconds you need before converting.

#### When GIF makes sense vs MP4 or WebM

GIF wins on universal autoplay. It plays inline in every email client, every chat platform, every CMS, and every browser back to Netscape. No <video> tag, no autoplay muted playsinline dance, no codec licensing. For a 2-second product demo inside a GitHub README, a Stripe Slack notification, or a marketing email, GIF is still the lowest-friction format in 2024.

Where GIF fits: GitHub READMEs (no video player), Slack and Discord chat (inline preview), Notion/Confluence docs (lightweight embed), email newsletters (most clients still block <video>), Twitter/X DMs, support ticket attachments. Anywhere the consumer might be a mail client or aggressive corporate sandbox.

Where MP4/WebM wins by a wide margin: any web page where you control the markup (use <video autoplay muted loop playsinline>), Twitter/X tweets (they auto-convert uploaded GIFs to MP4 anyway), Instagram and TikTok (video-native platforms), product landing pages, blog posts on your own domain. MP4 H.264 at the same visual quality is typically 10–50× smaller than the equivalent GIF.

WebP animation is the modern compromise: GIF-like autoplay semantics, MP4-like compression, supported in every browser since 2021 and in iOS Mail and Slack. If your target platform supports WebP (most do now), prefer it — but GIF is still the only safe bet for unknown-environment delivery like email and legacy systems.

#### Frame rate, dimensions, and palette tradeoffs

GIF's compression is indexed-color RLE with LZW. Each pixel is one of 256 palette entries, and runs of identical pixels compress well. This means file size scales roughly with frames × pixels × palette diversity. Halving any one of those approximately halves the size. The art is picking which to cut without ruining the result.

Frame rate: video sources are usually 24, 30, or 60 fps. GIFs rarely need more than 12-15 fps — the human eye barely sees the difference for short loops, but file size drops proportionally. For UI demos with cursor motion, 10 fps is often enough. For sports or fast action, push to 15 fps; above 20 fps the size penalty rarely justifies the smoothness gain.

Width is the highest-leverage knob. A 1080p GIF is roughly 9× the size of a 360p GIF at identical frame count and palette. For GitHub READMEs use 600-800px. For Slack/Discord reactions use 300-480px. For email signatures use 200-320px. Always downscale at the source rather than letting the platform downscale on display.

Palette generation matters more than people realize. Desktop FFmpeg can build a custom 256-color palette per clip in two passes (palettegen + paletteuse), which beats a naive single-pass conversion on gradients. ConverterUp uses FFmpeg's standard GIF encoder with Lanczos scaling, which works well for UI demos, screen recordings and reactions; for gradient-heavy footage, keep the width modest and expect some banding.

#### Common GIF issues: banding, size, audio loss

Color banding in gradients is GIF's signature failure mode. A smooth sunset or skin-tone gradient turns into visible 5–10 px color bands because 256 palette colors cannot represent millions of shades. The fix is to reduce the gradient's prominence — crop or reframe so the gradient is a small portion of the frame, lower the width, or accept the banding as part of the GIF aesthetic.

Files larger than expected are almost always caused by: dimensions too high (the #1 cause), frame rate above 15 fps, complex backgrounds with film grain (every frame has a different pseudo-random pattern, which destroys RLE compression), or a long duration. If your 4-second clip is >5 MB, drop the width by 30 % first, then the frame rate.

Audio is permanently lost because GIF has no audio container. ConverterUp drops the audio track silently. If your demo relies on audio (e.g., a sound effect at a specific moment), export to MP4 or WebM instead. There is no workaround — GIF89a simply has no audio spec.

Looping vs single play: GIF supports infinite loop, fixed N-loop, or single play via the Netscape Application Extension block. ConverterUp exports GIFs that loop forever, because almost every use case wants it (reactions, demos, microinteractions).

**Q: How long can the source video be?**

There is no fixed duration limit, but GIFs above 10-15 seconds tend to grow very large. For longer clips consider lowering the width to 320-480 pixels and the frame rate to 10-12 fps.

**Q: What is the maximum upload size?**

Source files up to 100 MB. The actual processing speed depends on your device's CPU and available memory because FFmpeg runs locally; files above 20 MB can take noticeably longer on phones.

**Q: Why is my GIF file so big?**

GIF is an old format with poor compression. To reduce size, lower the frame rate, shrink the width, or trim a shorter segment. For modern use cases, exporting to WebP or MP4 yields much smaller files.

**Q: Which video formats are supported?**

Input: MP4, WebM, MOV, AVI, MKV, FLV, M4V, 3GP, WMV and TS. Output: animated GIF. Audio tracks are dropped automatically since GIF does not support sound.

**Q: Should I use GIF or animated WebP in 2024?**

Use WebP when you control the rendering surface (your own website, app, modern email). It compresses 3–5× better than GIF, supports 24-bit color and alpha, and animates correctly in every modern browser. Use GIF only when the target environment is unknown or known-legacy (older email clients, ancient CMSes, GitHub README which auto-renders both but GIF has 100 % support).

**Q: Can I choose the GIF frame rate and size?**

Yes. Pick the frame rate (fps) — higher is smoother but produces a larger file — and the output width in pixels; the height scales automatically to keep the video's proportions. Lower fps and a smaller width are the fastest ways to shrink a GIF.

### Free QR Code Generator — No Expiration, Custom Logo

URL: https://converterup.com/tools/qr-code-generator

Generate QR codes online for any link or text — URLs, messages, and even Wi-Fi or contact-card strings you paste in. ConverterUp's QR code generator lets marketers, restaurant owners, and developers create scannable codes with custom foreground and background colors, adjustable size, an optional center logo, and four error correction levels. Type or paste your content, tweak the appearance, preview in real time, and download a high-resolution PNG ready for print or web. Everything is generated locally in your browser, so the URLs and personal data you encode are never logged or sent anywhere.

#### When QR codes actually pay off

QR codes shine in offline-to-online contexts where typing a URL is friction: restaurant menus, museum exhibits, conference posters, packaging inserts, receipts, business cards. A scan replaces a 40-character URL with a one-second camera point.

Wi-Fi onboarding is one of the highest-utility uses. Paste a string in the standard format WIFI:T:WPA;S:NetworkName;P:password;; into the text field and guests join your network without typing the password. Both iOS and Android camera apps support this format natively since 2018.

vCards (BEGIN:VCARD…END:VCARD) save contact info into the scanner's address book with one tap, and a WhatsApp link (wa.me/number) opens a chat directly. ConverterUp encodes whatever text you paste, so any of these formats works — there are no special forms, just paste the finished string or link.

Where QR codes don't pay off: anywhere users are already on a screen (use a hyperlink), behind glass or at awkward angles (scan quality degrades fast), or as a substitute for a short memorable URL on a billboard read at 60 mph.

#### Error correction levels — L, M, Q, H

QR codes embed Reed-Solomon error correction so they remain scannable when partially damaged or obscured. There are four levels, each trading capacity for resilience: L recovers ~7 %, M ~15 %, Q ~25 %, H ~30 %.

Use L for clean, digital-only contexts (websites, in-app displays) where you want the smallest possible code and maximum data capacity. Use M as a general-purpose default — it survives minor smudges and is what most browsers' built-in generators produce.

Use Q when the code will be printed and might get creased, splashed, or partially obscured (table tents, sticker labels, packaging). Use H when you need to overlay a logo in the center of the code — the higher correction lets the scanner reconstruct the masked area.

Higher correction does not make a code easier to scan in low light or at a distance — for that, increase the module size. Higher correction simply means more redundancy bytes, which makes the matrix denser and may require a larger printed size to keep individual modules readable.

#### Design tips: contrast, size, and logo overlays

Contrast is the single most important factor for scan reliability. Aim for at least 4:1 contrast ratio between foreground and background — dark modules on a light background. Inverted (light on dark) codes work but many older scanners struggle, so avoid for print.

Minimum physical size: as a rule of thumb, the code's side length should be at least scan_distance / 10. A code scanned from 30 cm needs to be at least 3 cm across; a code on a poster scanned from 3 m needs 30 cm. Always include a quiet zone of 4 modules around the code — without it, scanners may miss the edges.

Logo overlays work because of error correction, but keep the logo to ~20 % of the code's area max when using level H, and always test with multiple scanner apps (iOS Camera, Google Lens, dedicated apps) before printing. Place the logo dead center; off-center overlays disrupt the finder patterns and reliably break scans.

**Q: How does error correction level affect the QR code?**

Higher levels (Q, H) make the code readable even when partially damaged or covered by a logo, at the cost of denser modules. Use L or M for clean digital displays and H for printed codes that may get scratched.

**Q: What is the maximum amount of data I can encode?**

QR codes can hold up to about 4,296 alphanumeric characters or 2,953 bytes. ConverterUp picks the smallest version that fits your data; for long URLs, consider a URL shortener to keep the code readable.

**Q: Are the QR codes I generate tracked?**

No. Codes are rendered entirely client-side and never sent to a server. ConverterUp does not insert tracking redirects, so the URL you scan is exactly the URL you typed.

**Q: Which output formats are available?**

PNG, at the size you choose, which works for both web and print. For large posters, pick the largest size so the modules stay crisp. SVG export is not available.

**Q: Can I make a Wi-Fi QR code?**

Yes. Type the network details in the standard format WIFI:T:WPA;S:NetworkName;P:password;; (use WEP or nopass for other networks) into the text field. iOS and Android camera apps recognize it natively and offer to join the network — no third-party app needed.

**Q: Will the QR code still work if I change the background color?**

Yes, as long as foreground/background contrast stays above ~3:1 and the foreground is darker than the background. Pastel codes on white scan fine; light-on-dark inverted codes are riskier with older scanners. Always test with at least two scanner apps before going to print.

### YouTube Thumbnail Downloader — HD & Max-Res, Free

URL: https://converterup.com/tools/youtube-thumbnail-downloader

Download YouTube thumbnails in every available resolution with a single video URL. ConverterUp's YouTube thumbnail downloader is useful for content creators, journalists, and educators who need to reuse cover art for blog posts, podcast notes, video reactions, or TikTok and Reels edits. Paste the link, pick from Max Resolution (1280 × 720), Standard, High, Medium or Default versions, and save the JPG image directly to your device. The tool only requests YouTube's public thumbnail URLs, so no personal data, login, or API key is ever required to grab the image.

#### Available resolutions and YouTube's URL pattern

YouTube exposes every public thumbnail at predictable URLs based on the video ID. The pattern is https://img.youtube.com/vi/<ID>/<variant>.jpg. There is no auth, no API key, and no rate limit on these endpoints — they are designed to be embedded.

The variants, from largest to smallest: maxresdefault (1280 × 720), sddefault (640 × 480), hqdefault (480 × 360), mqdefault (320 × 180), and default (120 × 90). YouTube also generates auto-still frames at 1.jpg, 2.jpg, and 3.jpg — three frames sampled from the video, used as fallback thumbnails before the uploader picks a custom one.

Newer videos may also include WebP variants under vi_webp/ instead of vi/ for smaller file sizes. ConverterUp downloads the standard JPG versions from vi/, which every video has and every app can open.

maxresdefault is only generated when the uploader provides (or YouTube extracts) a source frame of at least 1280 × 720. For older videos, mobile uploads, and Shorts, maxresdefault may 404 — fall back to hqdefault.jpg, which is guaranteed to exist for every public video.

#### Fair use, attribution, and reuse rules

YouTube thumbnails are copyrighted by the uploader. The thumbnail is a creative work, just like the video itself. Downloading the image does not grant you a license to republish it as if it were your own.

Fair use (US) and equivalent fair-dealing doctrines (UK, Canada, Australia) generally permit reuse for commentary, criticism, news reporting, and education — for example, a blog post reviewing a video can show its thumbnail as context. The four fair-use factors (purpose, nature, amount, market effect) favor transformative, non-commercial commentary.

What is not fair use: using a popular video's thumbnail as the cover image of your own unrelated content, especially if it implies endorsement or association. Some creators issue DMCA takedowns for thumbnail reuse on competing channels — be careful with reaction videos and Shorts that copy thumbnails verbatim.

When in doubt, ask the creator for permission, attribute clearly (channel name + link), or use the thumbnail as part of an obvious quote rather than a standalone hero image.

#### Common gotchas: Shorts, private, age-restricted

Shorts use vertical 9:16 source frames, but YouTube still generates horizontal thumbnails by letterboxing or cropping. The maxresdefault.jpg for a Short is a 1280 × 720 image with the vertical content centered between black bars — not the vertical cover the Shorts app shows. There is currently no public endpoint for the vertical version.

Private and unlisted: private videos return 404 for every thumbnail variant. Unlisted videos behave like public ones for thumbnail URLs — anyone with the video ID can fetch them, which is sometimes a privacy surprise for uploaders.

Age-restricted videos sometimes block thumbnail access depending on YouTube's current policy. Region-locked videos still expose thumbnails globally because the CDN that serves img.youtube.com is not the same as the one serving the video stream. Deleted videos return 404 immediately; if you need the thumbnail of a removed video, only Wayback Machine snapshots can help.

**Q: Which thumbnail resolutions are available?**

Max Resolution (1280x720), Standard (640x480), High Quality (480x360), Medium Quality (320x180), and the default 120x90. Nothing larger exists — YouTube does not publish 4K thumbnails. Not every video has the Max Resolution version, especially older or low-resolution uploads; only the sizes that exist are shown.

**Q: Can I use these thumbnails in my own videos or articles?**

Thumbnails are protected by copyright and belong to the original uploader. Use them under fair use rules for commentary, news, or reviews, or ask the creator for permission before reusing as your own cover.

**Q: Does this work for unlisted or private videos?**

No. The downloader only fetches thumbnails that YouTube exposes publicly. Unlisted videos with a known URL usually still work, but private and age-restricted videos do not return a thumbnail.

**Q: Why is the thumbnail blurry?**

If only the lower-resolution images appear, the uploader did not provide an HD thumbnail. Try the High Quality version (480x360), which is available for almost every video, or upscale the image with the image resizer.

**Q: Can I extract video IDs from a Shorts or playlist URL?**

Yes for Shorts: the tool reads youtu.be/, youtube.com/watch?v= (including watch links that belong to a playlist), youtube.com/shorts/, youtube.com/embed/ and youtube.com/v/. Playlist-only links without a video ID are not supported — open the video and paste its link.

**Q: Why is the maxresdefault image returning a generic gray icon?**

YouTube returns a small 120 × 90 placeholder image instead of a proper error when a size does not exist. ConverterUp checks each image's real dimensions and hides sizes that only return the placeholder, so the list you see contains only real thumbnails.

### Remove EXIF Data — Photo Metadata Viewer & Remover

URL: https://converterup.com/tools/exif-viewer

View and remove EXIF metadata from photos online to protect your privacy before sharing images. ConverterUp's EXIF viewer reads JPEG, PNG, WebP, and TIFF files and shows camera model, lens, exposure settings, timestamps, and GPS coordinates that may have been embedded automatically. Photographers can audit their workflow while regular users can strip sensitive data with one click before posting on social networks or sending photos by email. The original file is read locally and the cleaned copy is generated in the browser, so your photo never reaches an external server.

#### What is EXIF metadata and why it matters

EXIF (Exchangeable Image File Format) is a structured block of metadata embedded inside most JPEG, TIFF, and HEIC photos by cameras and smartphones. It records what gear shot the photo (make, model, lens, focal length), how (ISO, aperture, shutter speed, white balance), when (timestamps in local and UTC time), and — most sensitive — where, via GPS coordinates accurate to a few meters.

EXIF is invisible in normal photo viewers but is trivially readable by anyone with a free tool. Posting a screenshot of your kitchen, your kid's school, or your home office can publish your exact address if you forgot to strip it. Journalists, activists, and anyone sharing personal photos online have a clear reason to audit metadata before publishing.

Beyond privacy, photographers use EXIF for workflow audits — verifying that a delivery came from the right camera body, checking that copyright fields are set, or confirming the capture date of a remote shoot. The viewer lists the key tags it finds — camera, lens, exposure, dates, software, copyright and GPS location — in one report.

#### How to remove EXIF data from photos

Upload a JPEG, PNG, WebP, or TIFF file, review the metadata report, then click Remove EXIF Data to download a clean copy. The clean copy is redrawn from the photo's pixels, so no metadata travels with it: PNG stays lossless, while JPEG, WebP and TIFF are saved as a high-quality JPEG (95%).

Because the photo is redrawn in the orientation you see on screen, it still appears right-side up on every platform. Everything else is left behind: GPS, timestamps, camera make and model, lens info, serial numbers, software fingerprints, and embedded thumbnails (which can leak the original even after edits).

Removal is all-or-nothing: the clean copy carries no metadata at all. If you only want to stop recording location but keep camera data, turn off geotagging in your phone's camera settings (see below) — new photos will keep gear info without GPS.

#### Privacy tips for sharing photos online

Most social networks (Instagram, Facebook, Twitter/X) strip EXIF on upload, but cloud drives, direct file attachments, email, Telegram, Signal in file mode, and WhatsApp document mode do not. Strip metadata yourself before sharing if there is any chance the original file will leave the platform unchanged.

Disable geotagging at the source on your phone for sensitive locations: iOS Settings → Privacy → Location Services → Camera → Never (or While Using App for travel photos). Android: open Camera app → Settings → Location tags → off. This prevents the problem before it starts.

When publishing screenshots of your screen, remember EXIF is not the only leak. Window titles, tab favicons, notification badges, and timezone offsets in dates can all reveal information. Combine EXIF stripping with manual review before posting anything tied to your identity.

**Q: What kind of metadata is stored in EXIF?**

EXIF can include the camera make and model, lens, ISO, shutter speed, aperture, focal length, capture date, software used, and precise GPS coordinates. Smartphones often add the location automatically unless you disable it in system settings.

**Q: Are HEIC, RAW, or CR2 files supported?**

RAW formats (CR2, NEF, ARW, DNG) and HEIC are not supported because they require vendor-specific decoders. Use JPEG, PNG, WebP or TIFF — convert RAW or HEIC to JPEG first (the HEIC to JPG tool strips metadata on its own).

**Q: Does removing EXIF affect image quality?**

Not visibly. The clean copy is redrawn from the pixels: PNG stays lossless, and JPEG, WebP and TIFF photos are saved as JPEG at 95% quality, which is indistinguishable from the original for practically every photo. The file is often smaller because the metadata block is gone.

**Q: Will the cleaned photo still display correctly on social media?**

Yes. The photo is redrawn in the orientation you see, so it stays right-side up everywhere, while GPS, timestamps and camera info are removed.

**Q: Can I remove EXIF from several photos?**

One photo at a time: drop a photo, remove the metadata, download the clean copy, then drop the next one. Each photo takes about a second, and nothing is uploaded.

**Q: Are my photos uploaded to a server?**

No. The file is read and decoded in your browser. Metadata parsing and removal happen entirely client-side — ConverterUp has no upload endpoint and no log of your photo's contents or metadata.

### Color Palette from Image — Extract HEX, RGB, HSL

URL: https://converterup.com/tools/color-palette

Extract color palettes from images online to find dominant colors for branding, web design, or moodboards. ConverterUp's color palette tool analyzes any uploaded photo and returns its eight most representative colors with HEX, RGB, and HSL values ready to copy. Designers can build a swatch from a product photo, illustrators can sample from reference art, and developers can pull theme colors from a screenshot. The image is processed entirely in the browser using a clustering algorithm, so private screenshots and unreleased artwork never get uploaded to a remote service.

#### How color palette extraction works

The extractor runs k-means clustering (with k-means++ initialization) on a downsampled copy of the image. Similar pixels are grouped into eight clusters and the center of each cluster becomes a palette color, together with the share of the image it covers. The result emphasizes coverage rather than vibrancy — large muted regions (sky, walls, skin) tend to rank above small saturated accents.

If you want vivid accent colors instead of dominant ones, crop the image to the region that contains them before extracting — for example just the logo or the product, not the background.

Every pixel is processed locally in your browser, so the image never reaches a remote server. That matters when you are sampling unreleased product photos, internal mockups, or screenshots with sensitive content.

#### Use cases: branding, UI themes, moodboards

Brand discovery: drop a hero photo, screenshot of a competitor's homepage, or product render and pull the colors that drive the visual identity. Copy the HEX values straight into a Figma styles panel or a Tailwind config.

UI theming from a screenshot: developers can pick a primary, secondary, and accent color from any mockup with a few clicks instead of pixel-peeping with the eyedropper.

Moodboards and editorial design: photographers and illustrators can build cohesive palettes from a reference image, copy the values into InDesign, Photoshop, or Procreate, or download the palette as a PNG swatch image.

Accessibility checks: pair extracted colors with a contrast checker before locking them into a design system. A palette that looks good on a hero image often fails WCAG when used as text on a light background.

#### HEX, RGB, HSL — which color format to copy

HEX (#2DD4BF) is the most compact and universal — CSS, design tools, brand guidelines, and Tailwind all accept hex. It is the default when in doubt.

RGB (rgb(45, 212, 191)) is preferred when you need to expose an alpha channel via rgba(), or when working with image-processing libraries that operate on 0–255 channels directly.

HSL (hsl(172, 66 %, 50 %)) describes color in human terms — hue, saturation, lightness — making it the easiest format to edit. Shift hue by 30° for an analogous color, drop lightness by 10 % for a darker shade, all without leaving the format.

**Q: How does the tool pick the dominant colors?**

It uses k-means clustering: similar pixels are grouped into eight clusters and the center of each cluster becomes a palette color, shown with the share of the image it covers. The result emphasizes coverage rather than vibrancy, so muted backgrounds may rank above accent colors.

**Q: How many colors does it return?**

Eight colors, ordered by how much of the image each one covers, with the percentage shown next to every swatch.

**Q: Can I extract a palette from a screenshot?**

Yes. Save the screenshot as PNG or JPG and drop it into the tool. Images from remote URLs need to be downloaded first because of browser cross-origin restrictions.

**Q: Can I use the palette in Figma or Tailwind?**

Yes. Click any HEX, RGB or HSL value to copy it and paste it into Figma, your Tailwind config or plain CSS. You can also download the whole palette as a PNG image to share it or drop it into a moodboard.

**Q: Are my images sent anywhere?**

No. The image is decoded by the browser, downsampled in memory, and analyzed locally. ConverterUp never receives the file or the resulting palette.

**Q: Which image formats can I analyze?**

PNG, JPG/JPEG and WebP. For best results use a clean image without heavy watermarks, since text overlays and logos can be picked up as their own color cluster.

### Favicon Generator — All PNG Sizes + Apple Touch, Free

URL: https://converterup.com/tools/favicon-generator

Generate a favicon package online from a single source image, ready to drop into any website or web app. ConverterUp's favicon generator produces eight PNG sizes from 16x16 up to 512x512 — including the 180x180 Apple touch icon and the 192/512 Android and PWA icons — plus an HTML snippet with the link tags to paste into your page. Designers and developers save time by skipping multiple manual exports in image editors. Conversion runs in the browser, so unreleased logos and brand assets remain private and are never stored on a remote server.

#### Why favicons still matter in 2026

A favicon is the tiny visual anchor that distinguishes your site in browser tabs, bookmarks, history pickers, and tab-overflow menus. With users routinely keeping 30+ tabs open, the favicon is often the only visible part of your brand for hours at a time. A missing or generic favicon is a small but constant signal that the site is amateur.

Beyond browser tabs, favicons drive the icon on iOS and Android home screens when users 'Add to Home Screen', the tile on Windows Start menu pins, the icon in macOS Dock when a PWA is installed, and the avatar in search results that some browsers (Chrome, DuckDuckGo) render next to organic listings.

For PWAs, the manifest icons are load-bearing: without 192 × 192 and 512 × 512 icons declared in manifest.json, the browser will not show the install prompt and Lighthouse will fail the installability audit.

A coherent favicon package also signals attention to detail to the people who matter most for first impressions — recruiters opening your portfolio, customers landing from a Google ad, journalists checking a source. The marginal cost (one source image, one upload) is rounded to zero; the cost of not doing it is a 404 in the network tab and a generic globe in the tab.

#### Required sizes for modern browsers and OS

16 × 16 and 32 × 32 — classic browser tab favicons. 32 is the modern default; 16 is the fallback for legacy DPI. Modern browsers accept PNG favicons declared with link tags; if you also want a favicon.ico at the site root for old clients, convert the 32 × 32 PNG to ICO with any ICO converter.

180 × 180 — Apple Touch Icon, used by iOS Safari for Home Screen shortcuts. Apple no longer needs separate sizes for each device since iOS 11; 180 is the one to ship.

192 × 192 and 512 × 512 — Android home screen and PWA install icons, declared in the web app manifest. The 512 also doubles as the splash screen icon on Android and as the high-DPI source for desktop PWAs.

maskable variants — Android adaptive icons crop to a circle or squircle. Provide a maskable-purpose icon with a generous safe area (keep the logo inside the central 80 % of the canvas) so the OS does not crop the brand mark.

#### HTML installation: link tags, manifest, theme color

Drop the generated files into your site root and paste the link tags from the included favicon-tags.html into : the 16, 32 and 48 px PNG icons, the apple-touch-icon.png, and the 192 and 512 px icons.

For a PWA, add a manifest.webmanifest file yourself: declare name, short_name, start_url, display: "standalone", background_color, theme_color, and an icons array pointing to the 192 and 512 PNGs from the package.

Add <meta name="theme-color" content="#2DD4BF"> to set the browser chrome color on Android Chrome and recent versions of Safari. Provide media="(prefers-color-scheme: dark)" variants if your site has a dark mode so the toolbar tint matches both schemes.

**Q: What sizes are included in the favicon package?**

Eight PNG icons: 16x16, 32x32, 48x48, 64x64, 128x128, 180x180 (apple-touch-icon.png), 192x192 and 512x512, plus a favicon-tags.html file with the HTML link tags. Download each size individually or all of them as one ZIP.

**Q: What is the recommended source image size?**

Use a square image of at least 512x512 pixels, ideally as PNG or SVG with a transparent background. Smaller sources can be enlarged but will look blurry at the largest sizes.

**Q: Are SVG sources supported?**

Yes. Upload an SVG and the generator rasterizes it at each target size for crisp results. PNG, JPG and WebP are also accepted.

**Q: How do I install the favicon on my site?**

Extract the ZIP, copy the PNG files to your site's root or assets folder, and paste the link tags from favicon-tags.html into the head section of your HTML. For PWA installation, reference the 192 and 512 icons in your own web app manifest.

**Q: Why does my favicon not update after I replaced it?**

Browsers cache favicons aggressively — sometimes for weeks — independent of the regular cache. Force a refresh by versioning the URL (/favicon.ico?v=2), serving the file with a short Cache-Control max-age, or clearing the favicon cache (in Chrome DevTools: Application → Storage → Clear site data).

**Q: Do I still need favicon.ico if I provide PNG icons?**

Often yes: older browsers and many bots look for /favicon.ico at the site root by convention, and some platforms (RSS readers, link previewers, intranet tools) only check that path. ConverterUp generates PNG icons; convert the 32 × 32 PNG to ICO with an ICO converter if you need that legacy file.

### SVG to PNG Converter — Transparent Background, Free

URL: https://converterup.com/tools/svg-to-png

Convert SVG to PNG online and turn vector graphics into raster images for use anywhere PNG is needed. ConverterUp's SVG to PNG converter is ideal for exporting icons to design tools, generating social media previews, embedding logos in PDFs, or feeding artwork into platforms that do not accept SVG. Pick the output scale at 1x, 2x, 3x, or 4x for retina-ready exports, set a transparent or solid background, and download the result instantly. Conversion happens in your browser, keeping unreleased designs and proprietary icons completely private.

#### Why convert SVG to PNG at all

SVG is the best format for icons, logos, and illustrations on the web. But many destinations still reject or mishandle it: email clients (Gmail, Outlook, Apple Mail) strip SVG for security reasons; social media previews (OG images, Twitter cards) only accept PNG or JPG; print pipelines often need raster TIFF or PNG instead of vector.

Legacy tools — older versions of Microsoft Word, PowerPoint, and many CMS rich-text editors do not import SVG cleanly. Marketplaces (Etsy, Amazon, Shopify) require raster product images. Embed targets like Notion, Confluence, and many forum platforms also lack SVG support in inline contexts.

Even where SVG works, you sometimes want PNG for predictability: an SVG rendered in 2026 Chrome may look slightly different from the same SVG rendered in an iOS 14 Mail client because of feature support differences (filters, masks, CSS variables). Rasterizing once removes that variance.

The right pattern: keep the SVG as the master, export PNGs at the resolutions you actually need. Re-export when the master changes. Never edit the PNG directly — every PNG edit invalidates it as a derivative of the source.

#### Scale strategy for retina and high-DPI

An SVG has an intrinsic size (its viewBox or width/height attributes). At 1×, the PNG matches that size in pixels. At 2×, the PNG is twice as wide and twice as tall — exactly the source needed for an HDPI display showing the icon at its CSS size.

For modern websites, the safe default is to export at 2× the CSS display size. A 24 × 24 CSS icon needs a 48 × 48 PNG. For phones with 3× DPR (iPhone Pro models, recent Pixels), 3× is the conservative choice; the visual difference between 2× and 3× is barely perceptible at icon sizes, so 2× is usually a reasonable trade-off.

For print, calculate the target physical size and DPI: a logo printed at 4 inches wide on a 300 DPI brochure needs 1200 pixels across. Use the 4× setting, or scale up the SVG's width and height attributes in the source before converting if you need more pixels.

Do not over-scale: a 4096 × 4096 PNG of a 16 × 16 icon is wasteful and slow to decode. Match the scale to the actual destination. If the icon is used at multiple sizes, export each size individually (16, 32, 64, 128) rather than shipping one huge file.

#### Transparency, fonts, and external assets gotchas

Transparency: SVGs use a transparent background by default, and ConverterUp preserves the alpha channel in PNG output. If you need a solid background for platforms that flatten alpha (some print and email pipelines), pick a background color in the options. Watch out for SVGs that define an opaque <rect> as a background — those will keep that fill regardless of the export option.

Fonts: an SVG that references a font by name (e.g., font-family: "Inter") will render with that font only if the font is available in the browser. If you uploaded an SVG generated by Figma or Illustrator, convert text to outlines in the source app before exporting. Otherwise the PNG will use a substitute font and look wrong.

External assets: <image href="https://…"> tags pointing to remote URLs may be blocked by browser security (CORS or tainted-canvas). The safe pattern is to embed bitmap dependencies as base64 data URIs inside the SVG before exporting. Same for external CSS — inline all styles into the SVG document.

**Q: How does the scale option work?**

Scale multiplies the SVG's intrinsic dimensions: a 100x100 SVG at 4x becomes a 400x400 PNG. Higher scale produces sharper results on retina displays at the cost of file size.

**Q: Can I keep transparency?**

Yes. Leave the background option set to transparent and the PNG will keep the SVG's alpha channel. Switch to a solid color when exporting for platforms that flatten transparency.

**Q: Are external assets in the SVG supported?**

External images and remote fonts referenced via http URLs may be blocked by browser security. For reliable output, embed images as data URIs and convert text to outlines before exporting from your SVG editor.

**Q: What is the maximum SVG size I can convert?**

There is no fixed size limit. Very complex documents with thousands of nodes may render slowly on mobile, but typical icons and illustrations convert in under a second.

**Q: Can I paste SVG code instead of uploading a file?**

Yes. Switch to Paste SVG Code and paste the markup copied from Figma, Illustrator or your code editor. The output is always PNG — convert the PNG to JPG or WebP with the Media Converter if you need another format.

**Q: Why does my exported PNG look blurry compared to the SVG?**

Either the export scale is too low for the display you are viewing it on, or the SVG includes pixel-aligned strokes that lose snapping at non-integer scales. Try doubling the scale (1× → 2×) and check whether stroke widths in the source are whole pixels for the chosen scale.

### Image to Base64 Encoder — Data URI for HTML & CSS

URL: https://converterup.com/tools/image-to-base64

Convert images to Base64 strings online to embed them directly in HTML, CSS, JSON, or email templates. ConverterUp's image to Base64 tool generates a clean encoded string or a full data URI ready to paste into a stylesheet, an SVG sprite, or a markdown document. It is useful for offline-first apps, transactional emails that must work without external requests, and inlining tiny icons to save HTTP requests. The encoding runs entirely in the browser, so confidential mockups and internal screenshots never leave your machine.

#### When inlining as Base64 actually makes sense

Inlining shines for assets under 4 KB where the cost of a separate HTTP request (DNS, TCP, TLS, request headers) outweighs the 33 % size penalty of Base64 encoding. Tiny icons in CSS pseudo-elements, single-pixel transparency PNGs, and small spinners are the canonical examples.

Transactional emails are the second clear win. Email clients block external image requests by default until the recipient clicks 'load images', so inlined logos and icons render immediately. Combined with the fact that emails are often archived for years, inlining guarantees the image still renders in 2030 even if your CDN is gone.

Offline-first PWAs and single-file HTML reports (downloadable invoices, exported dashboards, PDF-as-HTML) benefit from inlining for the same reason: the document is self-contained and works without network. Same goes for signed bundles shipped as a single file.

Where inlining fails: any image above ~10 KB, anything reused across pages (you lose HTTP caching), animations and video frames, and anything that needs lazy-loading. For those, keep a real file and reference it by URL — the browser's HTTP cache will outperform inlining within 2-3 page views.

#### Performance tradeoffs you should know

Base64 encoding inflates binary data by exactly 33.3 %: every 3 input bytes become 4 output characters. A 9 KB PNG becomes a ~12 KB string. Gzip and brotli can claw some of that back (~10-15 % for typical image data) but you cannot recover the full overhead.

Cache loss is the bigger penalty for repeated assets. A 50 KB logo referenced as <img src="/logo.png"> is downloaded once and cached for every subsequent page view. The same logo inlined in 20 emails or 20 HTML pages is downloaded 20 times. For a single-page asset this does not matter; for shared assets it is a real bandwidth and parse-time cost.

CSS parse time grows non-linearly with stylesheet size on low-end devices. A stylesheet that grows from 50 KB to 200 KB because of inlined images can add tens of milliseconds to first paint on mid-range Android phones. Treat inlining as a budget, not a default.

Memory: the browser holds the decoded image data and the original Base64 string in memory until the document is parsed. For very large inlined assets this can briefly double memory use compared to a URL-referenced file.

#### Data URI structure and where to paste it

The data URI format is data:<mime>;base64,<encoded>. Example: data:image/png;base64,iVBORw0KGgo…. The MIME type tells the consumer how to interpret the bytes — image/png, image/jpeg, image/svg+xml, image/webp, etc. Get the MIME wrong and the browser will refuse to render the image even if the bytes are correct.

In HTML: <img src="data:image/png;base64,…" alt="...">. In CSS: background-image: url("data:image/png;base64,…");. In JSON: store the full data URI as a string field, then assign it to the src at render time. In Markdown: ![alt](data:image/png;base64,…) works in most renderers but check that yours doesn't truncate long strings.

For SVG, prefer inlining the SVG markup directly (cheaper and stylable with CSS) over encoding the SVG as Base64. If you must Base64-encode an SVG, use image/svg+xml as MIME and consider URL-encoding instead — it produces a smaller, more readable result than Base64 for text-based formats.

**Q: When should I inline an image as Base64?**

Base64 makes sense for very small assets (under 4 KB) where a separate HTTP request would cost more than the size overhead. For larger images keep regular files because Base64 inflates size by about 33 %.

**Q: Is there a file size limit?**

There is no fixed size limit, but encoded strings grow about 33% larger than the file and become extremely long — most editors and email clients struggle past a few megabytes, so Base64 is best kept for small images.

**Q: What is the difference between a Base64 string and a data URI?**

A Base64 string is just the encoded bytes, while a data URI prepends the MIME type, like data:image/png;base64,.... Use the full data URI in src or url() and the raw string when you provide the type elsewhere.

**Q: Which image formats are supported?**

PNG, JPG/JPEG, WebP, GIF, and SVG. The MIME type in the data URI is set automatically based on the file you upload.

**Q: Can I copy the result directly into JSON without escaping?**

Base64 strings contain only A-Z, a-z, 0-9, +, /, and = — all safe inside a JSON string. The full data URI is also JSON-safe. The only character you may need to escape is the JSON quote that wraps the value itself; ConverterUp's copy buttons already produce a JSON-ready string.

**Q: Should I use Base64 or URL encoding for SVG inlining?**

Use URL encoding for SVG. SVG is text, so percent-encoding only the unsafe characters (%, #, <, >, quotes) produces a smaller and more readable result than Base64. Many SVG-to-data-URI tools default to URL encoding for that reason.

### Extract Frames from Video — Save as PNG/JPG, Free

URL: https://converterup.com/tools/video-frame-extractor

Extract frames from a video online to grab thumbnails, b-roll stills, or freeze frames for slides and articles. ConverterUp's video frame extractor reads MP4, WebM, and MOV files, lets you scrub through the timeline, and saves the current frame as a PNG or JPG. It is handy for journalists pulling stills from press footage, designers capturing reference frames, and content creators preparing thumbnails for YouTube, TikTok, or Reels. The video is decoded in the browser, so source clips and unreleased footage stay on your device throughout the process.

#### Use cases: thumbnails, b-roll, reaction stills, frame-by-frame editing

YouTube and TikTok thumbnails are the most common case. Scrub to the exact expression or composition you want, export as PNG at full source resolution, then bring into Photoshop or Figma for text overlay. A thumbnail pulled from the source is sharper than one re-extracted from a compressed upload, since you skip the second round of codec loss.

B-roll and editorial stills — journalists, documentary editors, and news producers pull frames from press conference footage or interview clips for use as standalone photographs in articles, social posts, and pitch decks. The frame extractor avoids the awkward screenshot-the-player workflow, which captures UI chrome and reduces resolution.

Frame-by-frame analysis — sports coaches, motion designers, animators, and VFX artists need to see exactly what happens between two motion-blurred frames. Step forward or back one frame (about 1/25 s), one second or five seconds with the buttons under the video to inspect a tennis serve, study an animation pose, or grab a hard-to-spot continuity error from a rough cut.

Reaction stills and meme generation — extract the single perfect facial expression from a podcast clip or a film scene to use as a chat reaction, blog header, or shareable image. The freeze-frame is often more usable than the moving clip itself in static contexts (email, PDF, print).

#### Codec and keyframe accuracy

Video codecs do not store every frame independently. Most frames are P-frames (predicted from the preceding frame) or B-frames (interpolated between past and future frames). Only I-frames (a.k.a. keyframes) are fully self-contained. To decode any frame, the decoder must walk back to the previous I-frame and replay everything in between.

H.264 typically places an I-frame every 2 seconds (~48–60 frames at 24/30 fps). Seeking is fast and frame-accurate because the GOP (Group of Pictures) is short. H.265 / HEVC uses longer GOPs (10+ seconds) to improve compression; seeking is slower because more frames must be replayed. AV1 can use even longer GOPs and is markedly slower to decode in the browser without hardware acceleration.

ConverterUp uses the browser's own video decoder: you seek to a moment, and the frame currently shown is drawn to a canvas at the video's native resolution. The step buttons move by about 1/25 of a second, which lands on a new frame for 24–30 fps footage. H.264 MP4 and WebM work in every modern browser; HEVC/H.265 depends on your browser and hardware.

Variable frame rate (VFR) clips — common in screen recordings, OBS captures, and phone videos with adaptive frame rates — have frames of different durations. A fixed step may occasionally land on the same frame twice or skip one; if that happens, nudge again with the one-frame buttons until the preview changes.

#### Capturing several frames at once

Capture as many frames as you need: move to each moment and click Capture Frame. Every capture is added to the Captured Frames gallery with its timestamp, where you can preview, download or delete it — useful for storyboards, contact sheets and thumbnail picks.

For a storyboard, step through the video in 5-second jumps and capture at each stop; for a precise moment, use the one-frame buttons. Scene cuts are the natural points to capture, since they give visually distinct frames.

Choose PNG for lossless, full-quality frames or JPG for smaller files. Remember that PNG frames from HD or 4K video are large — a dozen 4K PNGs can easily reach 100 MB, so use JPG if size matters more than perfect quality.

Download All as ZIP bundles every captured frame into one archive, with filenames that include the frame number and its timestamp (for example frame-001-00-01-23.png), so alphabetical order matches the order in the video.

**Q: What is the maximum video size?**

Up to 500 MB per file. Larger videos technically work but may take longer to seek because the browser has to demux the container in memory.

**Q: How accurate is the frame selection?**

The frame shown in the preview is exactly the one saved. Use the step buttons to move one frame (about 1/25 s), one second or five seconds forward or back for precise selection.

**Q: Can I export multiple frames at once?**

Yes. Capture each frame you want — they collect in the Captured Frames gallery — then click Download All as ZIP to get every frame in one archive.

**Q: Which video formats are supported?**

MP4, WebM and MOV, up to 500 MB. Codec support depends on your browser (H.264 and VP9 work everywhere). Output is PNG for lossless quality, with JPG available when you need a smaller file.

**Q: Does the extracted frame match the encoder's source quality?**

It matches the decoded source quality, which is the same picture the player shows. The frame is drawn to a canvas at the video's native resolution before being encoded as PNG (lossless) or JPG (high quality). For a 4K source, you get a 3840 × 2160 PNG — no extra compression is applied unless you choose JPG.

**Q: Why does my exported frame look slightly blurry compared to the playing video?**

Two likely causes. First, motion-blurred frames in 24/30 fps source are inherently blurred — that is how the camera captured motion, not a tool artifact. Second, some video players apply real-time sharpening or upscaling at render time that is not part of the underlying frame. Disable the player's enhancement filters or compare the extracted PNG side-by-side with the raw decoded frame in mpv/VLC.

### Stripe Fee Calculator 2026 — Free (USD/EUR/GBP/BRL)

URL: https://converterup.com/tools/stripe-fee-calculator

Calculate Stripe fees online for any transaction amount before you charge a customer. ConverterUp's Stripe fee calculator helps freelancers, SaaS founders, and online stores see the processing cost, the net amount they will receive, and the gross amount needed to net a target sum. Enter the amount, pick USD, EUR, GBP, or BRL, and review the breakdown instantly. The calculator uses Stripe's standard domestic card rate for each region; all math runs in your browser, so no transaction or customer information is ever logged.

#### Stripe pricing tiers: standard, international, currency conversion

Standard card rates are flat per region: 2.9 % + $0.30 in the US for domestic cards, 1.5 % + €0.25 in the EU/EEA for EEA cards, 1.5 % + 20p in the UK for UK cards, and 3.99 % + R$0.39 in Brazil. These tiers cover Visa, Mastercard, and most domestic schemes when the card is issued in the same country as your Stripe account.

International cards (card issued in a different country than your Stripe account) carry an extra 1.5 % surcharge in the US and 1.0 % in most of Europe. A US merchant accepting a French Visa pays 4.4 % + $0.30 instead of 2.9 % + $0.30. This is a real margin killer for SaaS targeting global audiences — model it upfront.

Currency conversion adds another 1 % on top when Stripe converts the charge to your settlement currency. If your account settles in USD and you charge a French customer in EUR, Stripe converts at the wholesale FX rate plus 1 % and applies the international surcharge. The compounded cost on a €100 charge can exceed 5.5 % all-in.

Amex, premium cards, and disputes sit outside the flat rate. Amex adds 0.5 % in the US. Premium and corporate cards add 0.5 % in Europe under interchange-plus pricing. Disputed chargebacks cost $15 per case (refunded if you win). For high-volume merchants, Stripe offers interchange-plus pricing that often saves 10–20 % vs the flat tier.

#### Reverse calculation: charge X to receive Y net

If you want a freelance invoice to net exactly $1,000 after Stripe takes its cut, you cannot simply add 2.9 % + $0.30 to $1,000 — that overshoots because the fee is calculated on the gross, not the net. The correct formula is gross = (net + fixed_fee) / (1 - percentage_fee). For US standard pricing, that means ($1000 + $0.30) / (1 - 0.029) = $1030.24.

ConverterUp's receive mode applies this formula to the standard card rate of the region you pick. The output is the exact gross amount to put on the invoice or charge button so the deposit lands at your target net. International-card and currency-conversion surcharges are not included — if they apply to you, add them on top.

Real-world use cases: setting freelance invoice amounts so you receive a round number, pricing a digital product so post-fee revenue hits a margin target, calculating refund amounts when a customer asks for partial reimbursement net of fees, and verifying that subscription pricing nets enough to cover hosting plus margin.

A common trap: Stripe's fixed fee ($0.30 in the US) is not refunded on full refunds in most regions since 2022. If a customer pays $20 and refunds, you lose the $0.30 permanently. For micro-transactions under $5, the fixed fee can exceed 6 % effective — small-ticket businesses should batch or set minimums to keep economics viable.

#### Stripe vs PayPal vs Square: where each wins

Stripe wins on developer experience, API breadth, and global currency support. Pricing is competitive at 2.9 % + $0.30 (US) and best-in-class for SaaS with built-in subscriptions, metered billing, tax calculation (Stripe Tax), and revenue recognition. The trade-off is no in-person POS hardware in most markets and a steeper integration learning curve than the alternatives.

PayPal matches Stripe's headline rate at 2.99 % + $0.49 (US standard) but the fixed fee is higher at $0.49, which hurts on small-ticket sales. PayPal's edge is the consumer-side wallet — buyers trust the PayPal checkout button, especially in eBay/marketplace contexts. Use PayPal as a secondary payment method to capture trust-skeptical buyers, not as primary processing.

Square charges 2.6 % + $0.10 (in-person) and 2.9 % + $0.30 (online) in the US. Its strength is integrated POS hardware (card reader, register, inventory) for restaurants and brick-and-mortar retail. For pure-online SaaS, Square has no real advantage over Stripe.

The 2024 reality: most SaaS and digital businesses run Stripe primary, add PayPal as a secondary checkout option to recover ~5–10 % of buyers who refuse to enter card details, and skip Square unless they have physical retail. Adyen and Braintree are alternatives for high-volume merchants (>$1M/year) where interchange-plus pricing offsets the higher integration cost.

**Q: Which Stripe pricing tiers does the calculator cover?**

Standard domestic card pricing: 2.9 % + $0.30 in the US, 1.5 % + €0.25 for European cards in the EU, 1.5 % + 20 p in the UK, and 3.99 % + R$0.39 in Brazil. International card, currency conversion and other surcharges are not included — check Stripe's pricing page for your account.

**Q: Does it support reverse calculations?**

Yes. Switch to receive mode, enter the amount you want to land in your account, and the tool will tell you exactly how much to charge so the net matches your target after fees.

**Q: Are subscription or invoice fees included?**

No. The calculator covers one-time card payments at the standard rate. Stripe Billing, Invoicing and other add-on fees are charged on top — add them to the result if they apply to your account.

**Q: Are my transaction amounts stored anywhere?**

No. Calculations happen client-side in your browser. ConverterUp does not log inputs and there is no server endpoint receiving the values you type.

**Q: Are Stripe fees refunded when I refund a customer?**

No, not since 2022 in most regions. When you issue a full or partial refund, Stripe keeps the percentage fee on the refunded portion and the entire $0.30 fixed fee. A $100 charge refunded in full means you are out roughly $3.20 permanently. Factor this into return policies and consider charging a small restocking fee on cancellations.

**Q: How do I reduce my effective Stripe fee rate?**

Three levers: enable Stripe Adaptive Pricing or local currency presentment so foreign buyers pay in their own currency without triggering the 1 % conversion fee on your side, negotiate interchange-plus pricing once you process >$80k/month (typically cuts 20–30 bp off flat rates), and route Apple Pay / Google Pay where possible since they sometimes carry lower interchange than raw card entry.

### Text Repeater — Copy Paste Repeat Text Free Online

URL: https://converterup.com/tools/text-repeater

Repeat text online to generate placeholder content, fill forms in bulk, or stress-test layouts with long strings. ConverterUp's text repeater accepts any input and duplicates it up to 10,000 times, joined by a new line, a space, a comma, or any custom separator you type. It is useful for QA engineers checking input limits, developers seeding databases, and writers creating long-form drafts. The text is processed entirely in your browser, so confidential prompts, internal copy, or test data never leave your machine.

#### Practical use cases for text repetition

Layout stress testing is the canonical case. UI engineers paste a 200-word paragraph and repeat it 50 times to confirm that long-form content does not break navigation, overflow flex containers, or hide CTAs below the fold. The same trick exposes truncation bugs in tables, card titles, and breadcrumbs when content exceeds the design's anticipated length.

Form and input limit verification — repeat a single character to a target length (5,000 chars, 65,535 chars, 10 MB) to confirm a server's maxlength, database column size, or API body cap is enforced as expected. This catches silent truncation bugs where a backend accepts the request but stores only the first N bytes.

Lorem Ipsum and placeholder generation — when the canonical Latin filler does not match the tone of the design, use the repeater to multiply a representative phrase or paragraph from your own product copy. The result reads more naturally during design reviews and surfaces typography issues that abstract Latin text does not.

ASCII art, separators, and divider lines — repeat - 80 times to draw a CLI banner, repeat = for section headers in Markdown READMEs, repeat • with a space for bullet rails. Repeating a Unicode glyph is faster than holding the key down in any editor.

#### Separators, numbering, and output formatting

The separator dictates how repetitions are joined. Space produces a single horizontal line (abc abc abc). New line creates a vertical list, one repetition per line — the default and the most useful option for bulk-paste workflows like seeding form fields or generating test rows. Comma produces a comma-separated list.

The custom separator accepts any string, including multi-character delimiters like " | " or " && " for shell pipelines, a semicolon for CSV-style lists, or "OR" to build a quick search query from repeated terms.

Need numbered items like item-1, item-2, …? The repeater copies your text exactly and does not add counters, so generate the numbered list in a spreadsheet (fill down) or with a short script, and use the repeater for identical copies.

Output formatting tips: for ID lists, use the new-line separator for clipboard-paste-into-spreadsheet workflows. For URL parameter testing, use the comma separator. For Markdown lists, set the input to - item and the separator to a new line; the repeater produces a valid bulleted list directly.

#### Why you should NOT use repetition for SEO

Repeating text for SEO is a 1998 trick that gets sites penalized in 2024. Google's spam policies explicitly flag scaled content abuse, thin content, and keyword stuffing. Pages built by pasting the same paragraph multiple times with minor variations rank for nothing and risk manual actions from Search Quality raters.

Duplicate content across pages on your own domain is not penalized directly, but it does cause canonicalization issues — Google picks one URL as canonical and ignores the others, wasting crawl budget. Repeated boilerplate inside a single page does not hurt rankings but does dilute the unique on-topic signal that ranking algorithms reward.

Legitimate SEO use of the repeater: generate filler for staging environments so you can test schema markup, OG tags, and pagination behavior without exposing draft content. Never publish auto-repeated text to production. If you need scale, write distinct content per landing page (programmatic SEO done right uses unique data per page, not repeated paragraphs).

If you are tempted to use repetition to meet a word-count target on a published page, stop — Google's Helpful Content system specifically targets pages that pad with filler to hit imagined length thresholds. Pages that answer the query concisely consistently outrank long-but-empty competitors after the March 2024 core update.

**Q: Is there a maximum number of repetitions?**

Up to 10,000 repetitions per run. For very large outputs, copy the result and paste it into a text editor; if you need more, run the tool again and append.

**Q: Which separators are available?**

New line, space, comma, and a custom field where you can type any character or string (for example a semicolon, a tab-like spacing or " | ").

**Q: Can I include line breaks in the input?**

Yes. Multi-line input is preserved exactly as typed and each repetition reproduces the full block. Combined with the newline separator, this creates well-formatted lists or paragraphs.

**Q: Does it work with non-Latin characters?**

Yes. The repeater is Unicode-safe and handles Portuguese accents, Spanish characters, Cyrillic, CJK, emoji, and right-to-left scripts without corruption.

**Q: Can I number each repetition automatically?**

No — the repeater produces identical copies. For numbered rows like row-001 to row-100, use a spreadsheet fill-down or a short script; the character and word counters under the output help you check the size of what you generated.

**Q: Can I repeat a string a non-integer number of times (e.g., 2.5x)?**

Not directly — repetition count must be a positive integer. For fractional repetition, repeat the full string the integer part of the count, then concatenate the first floor(len * 0.5) characters of the input. The tool does not automate this; it is a niche use case (typically for generating partial test payloads) better handled with a script.

### VTT to SRT Converter — Subtitles Online, Free

URL: https://converterup.com/tools/vtt-to-srt

Convert VTT to SRT subtitles online to make captions compatible with media players, editors, and platforms that reject WebVTT. ConverterUp's VTT to SRT converter parses cue numbers, timestamps, and styling, then rewrites them in the SRT format used by tools like VLC, Premiere Pro, and most TV media players. It is helpful for video editors importing browser-recorded captions and for translators delivering subtitle files to clients. Conversion runs locally in your browser, so dialogue from unreleased videos never gets uploaded.

#### WebVTT vs SubRip: format differences that matter

WebVTT (Web Video Text Tracks, .vtt) is the W3C standard built for HTML5 <track> elements. It opens with a mandatory WEBVTT header, uses dot separators in timestamps (00:00:01.500), and supports inline styling, cue positioning, CSS classes, region definitions, and chapter metadata. It is the only format YouTube exports for downloadable captions and the only format most browsers accept natively.

SubRip (.srt) is the older, simpler format. No header, no styling, comma separators in timestamps (00:00:01,500), and a sequential integer cue number before every block. SRT is what every editor (Premiere Pro, Final Cut, DaVinci Resolve, Avid) accepts on import, what set-top boxes and smart TVs read from USB drives, and what most translation agencies deliver.

Timing precision is identical — both formats use millisecond resolution (HH:MM:SS.mmm / HH:MM:SS,mmm). The only timestamp difference is the decimal separator, which is a one-character regex replace. Everything else that differs lives in the styling and positioning features that VTT adds and SRT lacks.

When you convert VTT → SRT, expect to lose: inline <c.classname> CSS classes, <v Speaker> voice tags, line: and position: cue settings, NOTE blocks, STYLE blocks, region definitions, and chapter markers. You keep: all dialogue text, timestamps, cue order, and basic line breaks within a cue. For 95 % of subtitle workflows this is a lossless round-trip.

#### Where each format is used in the pipeline

HTML5 video (<video><track src='captions.vtt'>) only accepts WebVTT. Chrome, Firefox, Safari, and Edge all refuse SRT directly. If you have SRT and need to display in a browser, convert to VTT first or use a player library (Video.js, Plyr) that does the conversion automatically at runtime.

YouTube accepts SRT, VTT, SBV, TTML, and SCC on upload, but exports only as SRT or VTT. Vimeo requires VTT for uploaded captions. Netflix, Disney+, Prime Video use their own broadcast-grade formats internally (IMSC, TTML, EBU-STL) but accept SRT and VTT as deliverables from translation partners.

NLE editors are SRT-first. Adobe Premiere Pro, DaVinci Resolve, and Final Cut Pro X import SRT directly into the captions track with frame-accurate timing. They also import VTT but discard styling. Avid Media Composer requires SRT or its proprietary .txt format. Going from a YouTube auto-caption (VTT) into Premiere for cleanup means converting to SRT first.

Media players: VLC, mpv, MPC-HC, and most smart TVs auto-detect a sidecar .srt file with the same name as the video. They also read VTT but the support is patchier on older firmware. For DVD/Blu-ray players reading subtitles from USB, ship SRT — it is the universal lingua franca.

#### Common conversion issues and how to fix them

BOM (byte-order mark) corruption is a common gotcha. VTT files exported from some tools start with a UTF-8 BOM (\uFEFF) that can break SRT parsers expecting a clean integer cue number on line 1. If you see 'Subtitle 1 has no number' errors in an editor, re-save the file as UTF-8 without BOM in a text editor.

Positioning cues lost — VTT lines like 00:00:05.000 --> 00:00:08.000 line:80% align:center become plain 00:00:05,000 --> 00:00:08,000 in SRT. If your VTT relied on positioning (e.g., to avoid overlapping on-screen text), the resulting SRT may place captions over the wrong area. Re-position in your editor after import.

Speaker tags (Hello!) have no SRT equivalent. If your editor expects John: Hello! instead, run a quick find-and-replace on the converted file to turn each  tag into a "Name:" prefix.

Overlapping cues — VTT allows two cues to display simultaneously (e.g., dialogue + on-screen text). SRT does not. ConverterUp keeps both cues in sequence with their original timestamps; if your player shows them flickering on top of each other, edit in your NLE to stagger or merge them.

**Q: What are the main differences between VTT and SRT?**

VTT uses a dot before milliseconds (00:00:01.500) while SRT uses a comma (00:00:01,500). VTT also supports inline styling and a WEBVTT header which SRT does not, so styling is stripped during conversion.

**Q: Will my cue styling and positioning be preserved?**

Plain text is kept intact, but VTT-specific cues such as line position, alignment, and CSS classes are removed because SRT does not support them. The result is clean, universally compatible subtitles.

**Q: Can I convert multiple files at once?**

One file at a time: upload or paste a VTT, then download or copy the SRT, and repeat for the next file. Each conversion is instant.

**Q: Is there a file size limit?**

There is no fixed limit — even a 4-hour film with thousands of cues converts instantly. Most subtitle files are well under 1 MB.

**Q: Does the converter handle non-Latin scripts and RTL languages?**

Yes. UTF-8 is preserved end-to-end, so Arabic, Hebrew, Chinese, Japanese, Korean, Cyrillic, and combined-mark scripts (Devanagari, Tamil) round-trip without corruption. RTL line direction is implicit in the characters themselves — SRT has no directionality marker, so renderers detect it from the first strong-directional codepoint.

**Q: Can I paste subtitles instead of uploading a file?**

Yes. Paste the VTT text into the input box and the SRT output appears next to it; copy it or download it as a .srt file. To shift timings, use your video editor or a subtitle editor after converting.

### JSON Formatter & Validator — View JSON Online Free

URL: https://converterup.com/tools/json-viewer

Format and validate JSON online with syntax highlighting and instant error reporting. ConverterUp's JSON viewer is built for backend developers, API consumers, and data analysts who need to inspect responses, beautify minified payloads, or quickly minify JSON before pasting it into a config file. Paste the text, prettify or minify it, and copy the result. The JSON is parsed locally in your browser, so private API responses, tokens, and customer data never reach a remote server.

#### When to use a JSON viewer

JSON is everywhere — REST APIs, NoSQL stores, config files, build outputs, log lines — but raw JSON is rarely human-readable. A dedicated viewer turns a flat blob into an indented, color-highlighted document, flags syntax errors as you type, and lets you switch between a pretty-printed view (for reading) and a minified view (for pasting into env vars or strings).

Typical tasks include inspecting an API response while building a frontend, comparing two payloads diff-style, hunting down a missing comma or extra bracket in a config file, validating that a webhook body matches a schema, and beautifying a one-line JSON dump pulled from a log aggregator.

ConverterUp's viewer runs entirely in your browser. Nothing is uploaded, nothing is logged. That matters when the JSON contains API keys, customer PII, or unreleased response shapes — exactly the cases where pasting into a random web tool would be reckless.

#### Features: format, validate, minify, highlight

Prettify indents the document with two spaces, useful for sharing in PRs or pasting into documentation. Minify strips all whitespace to produce the smallest possible payload, which is what you want for HTTP bodies, query strings, or copying into JSON-as-string fields.

Syntax highlighting colors keys, strings, numbers, booleans, and null distinctly so you can spot type mistakes at a glance. Expand the preview to read long payloads comfortably, or collapse it to keep the page compact.

Validation happens live as you type: a Valid / Invalid JSON badge shows the state, with the parser's error message when something is wrong. The viewer uses strict JSON parsing, so JSON5 quirks (comments, single quotes, hex numbers, trailing commas) are reported as errors rather than silently accepted.

#### Common JSON errors and how to fix them

Trailing commas — {"a":1,} is invalid JSON. Most languages and editors permit them, JSON does not. Remove the comma after the last item in any object or array.

Single quotes — {'a':1} looks fine in JavaScript but is not JSON. Keys and string values must use double quotes. Run a find-and-replace from ' to " if your source comes from a JavaScript dump.

Unescaped characters in strings — newlines, tabs, and backslashes inside string values must be escaped as \n, \t, and \\. Pasting a raw multi-line string is a frequent cause of unexpected token errors.

Missing brackets — large hand-edited files often end up with an unbalanced bracket or brace. The error message tells you where the parser gave up; from there, walk backward to find the unmatched pair.

**Q: How are JSON errors reported?**

The badge switches to Invalid JSON and the parser's message explains what went wrong, such as an unexpected token or an unexpected end of input. Fix the issue and the formatted preview updates automatically.

**Q: What is the maximum JSON size?**

There is no fixed limit; payloads of several megabytes format quickly on most laptops. Very large documents can make the highlighted preview slow to render — minify them or work with a smaller excerpt.

**Q: What is the difference between minify and beautify?**

Beautify (or pretty-print) adds indentation and line breaks so JSON is human-readable. Minify removes every byte of whitespace to produce the smallest valid payload — useful for HTTP bodies, environment variables, or copying JSON into a single-line string.

**Q: Does it support JSON5, JSONC, or comments?**

No. The viewer enforces strict JSON per RFC 8259, so trailing commas, single quotes, hex numbers, and comments are flagged as errors. Strip JSON5 / JSONC extensions in your source first, or use a JSON5-to-JSON converter before pasting.

**Q: Can I copy the formatted or minified JSON?**

Yes. Use Copy Formatted for the indented version or Copy Minified for the compact one-line version — both are copied straight to your clipboard.

**Q: Is my JSON sent to a server?**

No. Parsing, formatting, validation, and minification all run client-side. ConverterUp has no logging endpoint for JSON content, which is critical when debugging payloads with credentials, tokens, or PII.

### Hex to Decimal Converter — Free (Binary, Octal, RGB)

URL: https://converterup.com/tools/hex-to-decimal

Convert hex to decimal online and see the value in hexadecimal, decimal, binary, and octal in a single view. ConverterUp's number base converter is a quick reference for embedded developers, low-level programmers, and students working through assembly or networking exercises. Type a hex or decimal value and every base updates instantly; six-digit color codes like #FF5733 also show a color preview with the matching RGB values. Calculations run in your browser, so values never leave your machine.

#### Where base conversion shows up day-to-day

Debugging is the most common case. Stack traces show memory addresses in hex (0x7ffee5b3c000), registers in hex, flags as bitmasks. Translating to decimal helps spot patterns: a register holding 0x10000000 is bit 28 set, which often matches a flag definition in the source.

Networking and protocols use hex constantly: MAC addresses (00:1A:2B:3C:4D:5E), IPv6 (2001:db8::1), protocol numbers, port flags, MTU sizes, TCP flag bits. Wireshark dumps and packet captures are essentially walls of hex; conversion is required to interpret them.

CSS and design live in hex (#2DD4BF), occasionally in decimal-RGB (rgb(45, 212, 191)). A designer handing off a color and a developer reading the same color use different bases for the same value; conversion is part of the handoff.

Embedded and assembly work touches every base: hex for opcodes and memory, binary for bit manipulation, octal for legacy Unix permissions (chmod 755 is rwxr-xr-x = 111101101 binary = 0o755 octal). Mixing the bases without fluency is a recipe for off-by-one bugs.

#### Two's complement and signed integers

Modern CPUs represent signed integers using two's complement. To negate a number, flip every bit and add 1. In 8-bit, the value 0xFF is 255 unsigned but -1 signed; 0x80 is 128 unsigned but -128 signed. This is why an 8-bit signed integer ranges from -128 to +127 (not -127 to +127): the negative range has one more value.

When converting hex to decimal, you must know the bit width and signedness of the source. 0xFFFFFFFF is 4 294 967 295 as a 32-bit unsigned int, but -1 as a 32-bit signed int. ConverterUp shows the unsigned value, which matches how most hex literals are written in C and Go; to read a value as signed, subtract 2^N when the top bit is set (for 32 bits: value − 4 294 967 296).

The sign bit is always the most significant bit. In hex, that means the high nibble: a 32-bit hex value starting with 0x8… through 0xF… is negative when interpreted as signed. 0x7FFFFFFF is the maximum 32-bit signed int (2 147 483 647); add 1 and you wrap to 0x80000000, which is the minimum (-2 147 483 648).

When debugging integer overflow, look at the binary output to see the exact bit pattern. Overflow in two's complement is silent — the CPU does not raise an exception, the bits just wrap. A web form accepting a number into a 32-bit signed field will accept 2 billion and store 2 billion as expected; it will silently corrupt anything above ~2.1 billion.

#### Floats and color hex codes

Floating-point numbers in memory are not a simple base conversion of the decimal value. IEEE-754 single precision (32-bit float) splits 1 sign bit, 8 exponent bits, and 23 mantissa bits. 1.0 in IEEE-754 is 0x3F800000; 0.1 is 0x3DCCCCCD — the famously inexact representation that causes 0.1 + 0.2 !== 0.3 in JavaScript.

ConverterUp converts whole numbers; it does not decode IEEE-754 floats. If you have a hex dump of a float (for example 0x3F800000), use a dedicated float inspector or a line of code such as new DataView(buffer).getFloat32(0) to read it.

Color hex codes are a different and simpler beast: 3 bytes (RGB) or 4 bytes (RGBA), each in 00-FF. #2DD4BF means R=45, G=212, B=191. The 8-digit form (#2DD4BFCC) appends alpha. Modern CSS also supports the relative-color notation, but hex remains the most compact and most universally supported.

**Q: Does the converter handle negative numbers?**

No — it converts non-negative integers. For a negative number in two's complement, convert the unsigned hex value and subtract 2^N (256 for 8 bits, 65 536 for 16, 4 294 967 296 for 32) when the top bit is set.

**Q: What is the maximum value supported?**

Values are exact up to 2^53 − 1 (9 007 199 254 740 991, or 0x1FFFFFFFFFFFFF), the largest integer JavaScript represents safely. Beyond that the last digits may be rounded.

**Q: Can I convert color codes?**

Yes. Enter a six-digit hex color like #2E5C55 and the tool shows a color preview with the matching red, green and blue values (46, 92, 85), which you can copy as RGB.

**Q: Can I convert decimal to hex?**

Yes. Type in the Decimal field instead of the Hexadecimal one and the hex, binary and octal values update instantly. Each result has its own copy button.

**Q: Does the tool accept the 0x prefix or 0b notation?**

Hex input accepts 0x, #, or no prefix, in upper or lower case. Binary and octal are shown as results with their own copy buttons; the input fields are hexadecimal and decimal.

**Q: Can I convert binary or octal numbers?**

The results show binary and octal for any value you enter. To convert from binary or octal, use the dedicated conversion pages (binary to decimal, octal to decimal and others) linked below.

### HTML Minifier — Compress HTML Code Online Free

URL: https://converterup.com/tools/html-minifier

Minify HTML online to reduce page weight, save bandwidth, and improve Core Web Vitals scores. ConverterUp's HTML minifier removes comments and collapses whitespace — including the gaps between tags — while leaving your markup and attributes untouched. Front-end developers and static-site builders can paste their template, click minify, see the savings, and copy or download the smaller file. Minification runs in your browser, so proprietary markup, internal templates, and unreleased landing pages stay completely private.

#### What gets removed during minification

Whitespace is the biggest win. Hand-written HTML and template-engine output contain hundreds of newlines, tabs, and runs of spaces that the browser never renders. The minifier collapses every whitespace sequence to a single space and removes the whitespace between tags, typically shaving 15–25 % off raw size before gzip.

Comments () are stripped, including conditional comments for old Internet Explorer and server-side include directives — if your templates rely on those, keep them out of the minifier.

Optional tags per the HTML5 spec — the closing , , , , and several others — can be omitted because the parser infers them. ConverterUp does not remove them: it only strips comments and whitespace, which keeps the output safe to open in any editor.

Heavier optimizations — dropping redundant attributes like type='text/javascript', removing quotes around attribute values, collapsing boolean attributes — are left to build tools such as html-minifier-terser. ConverterUp keeps attributes exactly as written.

#### When NOT to minify HTML

Never minify the file you commit to source control. Minified HTML is unreadable, undiffable, and impossible to review in a PR. Keep the source template human-readable and minify only the build artifact that goes to the CDN. The same rule applies to email templates, MJML output, and JSX/template engine output.

Skip minification during local development. Source maps for HTML do not exist (unlike JS/CSS), so a broken minified template is much harder to debug than a broken source template. Most dev servers (Vite, Next.js, Astro) serve unminified HTML in development and minify only in production builds.

Avoid minifying inside template engines that depend on whitespace semantics. Liquid, Handlebars, EJS, and Jinja generally tolerate whitespace removal, but Pug/Jade and Slim are whitespace-sensitive by design — minifying their output post-render is fine; minifying the template itself is destructive. Same for Markdown and MDX sources.

Be careful with , , and white-space: pre CSS. Content inside these elements preserves whitespace semantically — a code block in a blog post relies on every space and newline. ConverterUp collapses whitespace everywhere, so minify pages with code blocks in your build pipeline instead, or paste only the parts without  content.

#### Build pipeline integration: where this fits

For one-off minification (a single template, an HTML email, a static landing page generated by a no-code tool), paste-into-ConverterUp is the fastest path. For ongoing production sites, minification belongs in the build step. Doing it manually after each deploy is error-prone and skips the source-map benefits.

Next.js, Astro, and Gatsby minify HTML automatically in production builds via html-minifier-terser. SvelteKit and Nuxt do the same. If you use these frameworks, the static output is already minified — paste-minifying again gains nothing. Webpack users add html-webpack-plugin with minify: true. 11ty users add an HTML transform that pipes the output through a minifier.

Server-rendered apps (Rails, Django, Laravel, Express + EJS) usually do not minify by default. The win from minifying server-rendered HTML is real (10–25 % on first-byte size) but small once gzip/brotli kicks in. Most teams skip it because the build complexity outweighs the byte savings on TLS+brotli connections.

Don't compare apples to oranges: a minified HTML file is smaller on disk, but the network savings after gzip/brotli are often only 2–5 % because compressors already deduplicate runs of whitespace. Minify to improve parse time in the browser more than to save bandwidth — the browser still has to read every byte.

**Q: How much can HTML usually be minified?**

Typical reductions are 15-30 % for hand-written HTML and up to 50 % for documents with heavy whitespace and HTML comments. Combine with gzip or brotli compression for additional savings on the wire.

**Q: Does minification break inline JavaScript or CSS?**

Inline scripts and styles are not rewritten, but their whitespace is collapsed like the rest of the document. Code that relies on line breaks — JavaScript without semicolons, or // single-line comments — can break, so minify pages with inline scripts in your build pipeline instead.

**Q: Are HTML comments removed?**

Yes, all of them — including conditional comments for old Internet Explorer. If a comment must survive (a license notice or a template directive), add it back after minifying.

**Q: What is the maximum HTML size?**

There is no fixed limit; documents of a few megabytes minify in well under a second. For production sites, make minification part of your build pipeline.

**Q: Does minifying HTML hurt SEO or accessibility?**

No, when done correctly. Search engines parse the DOM after the browser parses HTML, so whitespace and comments are invisible to them. Accessibility is unaffected because aria-* attributes, alt text, semantic tags, and the rendered text are all preserved. Only the bytes change.

**Q: Can I minify Handlebars, EJS, or other templated HTML?**

Often yes, because template tags such as {{ }},  and {% %} are left as they are — only comments and whitespace change. Check the output of whitespace-sensitive templates (Pug, Slim) and prefer minifying the rendered HTML rather than the source template.

### CSS Minifier — Compress Stylesheets Online Free

URL: https://converterup.com/tools/css-minifier

Minify CSS online to ship smaller stylesheets, reduce render-blocking time, and improve Lighthouse performance scores. ConverterUp's CSS minifier strips comments, removes whitespace and line breaks, tightens spacing around braces, colons, semicolons and commas, and drops the last semicolon in each rule. Front-end developers, theme authors, and WordPress users can paste a stylesheet, copy or download the minified result, and serve it from their site or CDN. The processing happens entirely in your browser, so internal design systems and client stylesheets are never uploaded to a third party.

#### What gets compressed in a CSS file

Whitespace and newlines are removed everywhere they are not significant — between selectors, before braces, after semicolons, inside calc() expressions where the spec allows it. The final semicolon before } is dropped because CSS treats it as optional. A typical 50 KB hand-written stylesheet shrinks to 30–35 KB from whitespace removal alone.

Comments (/* ... */) are stripped, including license comments that start with /*! — if you must keep a copyright header, add it back to the top of the minified file.

Color shorthand (#FFFFFF to #FFF, rgb() to hex) is a further optimization done by build tools such as cssnano or Lightning CSS. ConverterUp leaves colors exactly as written, which keeps the output predictable.

Numeric shorthand (0.5em to .5em, 0px to 0), merging duplicate selectors and collapsing margin: 10px 10px 10px 10px are also build-tool optimizations. ConverterUp focuses on safe whitespace and comment removal and does not rewrite values or selectors.

#### What this minifier changes — and what it leaves alone

ConverterUp applies only whitespace and comment transformations, so the computed styles are identical in every browser. The output is structurally compact but semantically the same as the input.

Deeper rewrites — merging rules with shared declarations, dropping outdated vendor prefixes, reordering declarations for better gzip — belong in a build tool like cssnano or Lightning CSS, where they run with full knowledge of your browser targets.

It does not remove unused selectors (that requires DOM analysis — use PurgeCSS), does not change specificity or selector order, does not inline custom properties (a --brand-primary stays a variable so runtime theme switching works), and does not touch vendor prefixes.

Real-world savings: a 100 KB unminified design-system CSS typically goes to 60 KB minified, 18 KB gzipped, 14 KB brotli. That last number is what the browser actually downloads on a modern HTTPS connection. Minification helps the parser unpack faster more than it saves bandwidth — gzip already deduplicates most of the whitespace wins.

#### Critical CSS vs full minify

Critical CSS is a different optimization than minification, often confused with it. Critical CSS extracts only the rules needed to render the above-the-fold content of a specific page, inlines that into a <style> tag in <head>, and lazy-loads the full stylesheet. This eliminates the render-blocking round trip and improves Largest Contentful Paint by 200–800 ms on slow connections.

You want both. Critical CSS reduces the bytes that block render. Minification reduces every byte. Combine them: extract the critical subset (12–20 KB raw), minify it, inline it. Load the rest of the stylesheet asynchronously with <link rel='preload' as='style' onload='this.rel="stylesheet"'> or modern media='print' onload='this.media="all"' hacks.

Tools for critical CSS: critters (used by Next.js when experimental.optimizeCss is on), critical (Penthouse-based, by Addy Osmani), beasties (active fork of critters). For static sites, run critical-CSS extraction per route at build time. For SSR apps, do it per page on first request and cache the result.

When critical CSS is overkill: small sites with a single global stylesheet under 30 KB. Inlining the whole thing is simpler than splitting it and the LCP gain is marginal. Critical CSS pays off when the full stylesheet is >50 KB and the home page only needs 15 KB of it.

**Q: How much can CSS usually be reduced?**

Expect 20-40 % size reduction on typical stylesheets. Combined with gzip or brotli compression on the server, most sites end up serving CSS under 30 KB even for full design systems.

**Q: Are CSS variables and modern features supported?**

Yes. Custom properties, calc(), nested at-rules, container queries, and CSS Layers are all kept, because only whitespace and comments change. Vendor prefixes are kept untouched so cross-browser compatibility is not affected.

**Q: Does it remove unused selectors?**

No. The minifier focuses on safe size reduction. Removing unused selectors requires knowing which HTML actually uses them, which only a tool like PurgeCSS can do during build time.

**Q: What is the maximum stylesheet size?**

There is no fixed limit; realistic design-system stylesheets minify instantly. Most production stylesheets are under 200 KB before minification.

**Q: Does the minifier create source maps?**

No. Source maps come from build tools (Sass, PostCSS, Vite, webpack) that know your original files. Use ConverterUp for quick one-off minification and keep source maps in your build pipeline.

**Q: Why does my minified CSS sometimes look smaller than expected?**

The most likely cause is that your input already contains few comments and little whitespace — typical of CSS that went through Sass or PostCSS, which produces semi-compact output even without an explicit minify step. The minifier still trims further, but the marginal gain on already-compact CSS is 5–10 % rather than the typical 30 %. Compare bytes pre- and post-gzip for a realistic comparison; the wire savings are usually similar regardless.

### UUID v4 Generator — Online, Bulk up to 100, Free

URL: https://converterup.com/tools/uuid-generator

Generate UUID v4 identifiers online for database keys, idempotency tokens, request IDs, and session tracking. ConverterUp's UUID generator creates one UUID or up to 100 at a time using the browser's cryptographically secure random source (crypto.randomUUID), so collisions are statistically impossible. Choose uppercase or remove the hyphens if your storage needs it, then copy one UUID or the whole list. Generation runs locally with no server round-trip, which guarantees that the IDs you receive are not logged, replayed, or reused anywhere outside your machine.

#### UUID versions: v1, v4, v7, and NIL

UUID v4 is the workhorse. 122 random bits plus 6 fixed version/variant bits, generated from a cryptographically secure RNG. Collision probability is so low (you would need to generate ~1 billion UUIDs per second for ~85 years to have a 50 % chance of a collision) that it can be treated as zero at internet scale. Use it as the default for almost everything.

UUID v1 encodes a 60-bit timestamp plus a MAC address and a clock sequence. It is sortable by creation time but leaks the host's MAC and the exact creation moment, which is a privacy concern. Most modern systems avoid v1 because of that leak and because the timestamp ordering is awkward (low bits come first).

UUID v7 (RFC 9562, 2024) is the modern alternative to v1: a 48-bit Unix-millisecond timestamp in the high bits, followed by random bits. It is lexicographically sortable, which makes it better for B-tree primary keys than v4. ConverterUp generates v4; if you need v7, most languages have a library for it (uuid in npm, uuid7 in Python).

NIL UUID (00000000-0000-0000-0000-000000000000) is a sentinel meaning 'no value' — useful as a default in optional FK columns or as a placeholder in tests. The Max UUID (ffffffff-ffff-ffff-ffff-ffffffffffff) is the equivalent ceiling sentinel for range queries.

#### UUID vs auto-increment integer IDs

Auto-increment integers (BIGSERIAL in Postgres, AUTO_INCREMENT in MySQL) are tiny (8 bytes), cache-friendly, and produce dense B-tree indexes. Their downside is that they leak business information — anyone seeing order=4217 can guess your order volume — and they make multi-master writes painful because the database server must coordinate the next value.

UUIDs are 16 bytes (2× the storage and index cost of a BIGINT), do not leak counts, can be generated client-side without a round-trip, and survive offline-first workflows where IDs need to exist before the row reaches the server. They are also URL-safe and globally unique across shards, services, and databases.

The pragmatic stack: UUID v7 for the primary key (good index locality, no count leak, client-generatable), an optional human-friendly BIGINT order_number column for display in the UI, and an optional opaque public_id (Nano ID or short hash) for URLs that need to look pretty.

Do not use UUID v4 as a primary key on a large hot table without thinking it through — its randomness causes severe write-amplification on B-tree indexes. Either use UUID v7, or use BIGINT primary keys with a separate UUID column for external references.

#### Storage formats: binary vs string, encoding choices

A UUID is fundamentally 16 bytes. Stored as a binary(16) or Postgres uuid type, it costs 16 bytes per row. Stored as the canonical hyphenated string (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx), it costs 36 bytes plus per-row overhead — more than 2× the binary cost.

On Postgres, always use the native uuid type — it stores binary internally, accepts string input/output transparently, and supports indexing and ordering correctly. MySQL has no native UUID type; use BINARY(16) with helper functions UUID_TO_BIN and BIN_TO_UUID, optionally with the rearrangement flag for index-friendly storage.

For APIs, return the hyphenated string form. It is the universal exchange format. Base64 or Base58 encodings produce shorter strings (22 and 22 chars respectively vs 36) but break tooling — debuggers, log greps, and SQL clients all expect the hyphenated form. Save the encoded short forms for URL slugs only.

**Q: Are these UUIDs safe to use as primary keys?**

Yes. UUID v4 has 122 bits of randomness from a cryptographically secure source, giving a collision probability low enough to be ignored at internet scale. They are widely used as primary keys in PostgreSQL, MongoDB, and DynamoDB.

**Q: How many UUIDs can I generate at once?**

Up to 100 per batch. Generate again for more; the list can be copied with one click and pasted into seed files or spreadsheets.

**Q: Can I generate other UUID versions?**

The tool generates UUID v4, the most common version in application code. You can switch to uppercase and remove the hyphens depending on your storage requirements.

**Q: Are the UUIDs cryptographically secure?**

Yes. They come from crypto.randomUUID, which uses the browser's cryptographically secure random generator — suitable for security tokens, session identifiers, and any case where guessability matters.

**Q: Can I get UUIDs without hyphens or in uppercase?**

Yes. Toggle Uppercase for XXXXXXXX-… output and turn off Include Hyphens for the 32-character form. The bytes are identical across formats — only the textual representation differs.

**Q: What is the actual collision probability for UUID v4?**

Negligible at any realistic scale. With 2^122 possible v4 UUIDs, generating 1 billion per second for 85 years gives a 50 % chance of a single collision. For a typical app generating millions per year, the probability is effectively zero — orders of magnitude less than the chance of a cosmic-ray bit flip in your database.

### Base64 Decode Online — Decode to Text or Image, Free

URL: https://converterup.com/tools/base64-decode

Decode Base64 strings online back to plain text or images, with automatic detection of data URIs. ConverterUp's Base64 decoder is useful for inspecting API responses, JWT segments, decoding email attachments, and extracting embedded images from CSS or HTML. Paste the encoded string, see the result instantly, and copy the text or download the decoded image. The decoding runs entirely in your browser, so sensitive tokens, customer payloads, and private images never get logged or transmitted to a remote server.

#### Where Base64 actually shows up

Data URIs embed images, fonts, and small files directly inside HTML or CSS as data:image/png;base64,iVBORw0KGgo…. Useful for icons under 4 KB that would otherwise cost an HTTP round-trip. Above 4 KB the encoding penalty (Base64 is 33 % larger than raw bytes) outweighs the round-trip savings, so use sprite sheets or HTTP/2 multiplexing instead.

HTTP Basic Auth sends credentials as Authorization: Basic <base64(user:password)>. This is encoding, not encryption — anyone with the header can decode the credentials in one step. Only safe over TLS. The decoder is the fastest way to inspect a curl -v dump and verify which user is being authenticated.

JWT tokens are three Base64URL segments separated by dots: header.payload.signature. Base64URL replaces + with - and / with _ and drops padding. To read a JWT here, paste one segment at a time after swapping - back to + and _ back to /, and add = padding until the length is a multiple of 4.

Email attachments over SMTP use Base64 (specifically MIME Base64 with line breaks every 76 chars) because SMTP was designed for 7-bit ASCII text. Cryptographic keys and certificates in PEM format (-----BEGIN PRIVATE KEY-----) are Base64 wrapped around DER binary. SVG inlining, CSP nonces, OAuth state tokens, WebAuthn credential IDs — Base64 is everywhere in modern web infrastructure.

#### Encoding vs decoding: direction matters

Encoding takes raw bytes (text, binary, image) and produces a Base64 ASCII string. The output is always 33 % larger than the input (3 input bytes → 4 output chars), padded with = to make the length a multiple of 4. Encoding is deterministic and lossless: encode then decode and you get the exact original bytes back.

Decoding reverses the process. Take 4 Base64 chars → produce 3 bytes. The input must be valid Base64 — characters outside A-Za-z0-9+/= make the decode fail, while spaces and line breaks are ignored.

Text encoding inside Base64 is a separate concern. Base64 encodes bytes, not characters. If you Base64-encode the string café, the result depends on whether you encoded UTF-8 bytes (Y2Fmw6k=) or Latin-1 bytes (Y2Fm6Q==). ConverterUp decodes as UTF-8 and, if the bytes are not valid UTF-8, shows them character by character as a fallback.

The padding question: standard Base64 always pads to a multiple of 4 with =. Base64URL (used by JWT, OAuth, WebAuthn) often strips the padding because URLs hate =. A string of length 22 needs 2 padding chars to reach 24 — add them before decoding if the tool reports invalid input.

#### Common gotchas: URL-safe, padding, line breaks

URL-safe Base64 (Base64URL, RFC 4648 §5) replaces two characters: + → -, / → _. The padding char = is also typically dropped. ConverterUp expects standard Base64, so convert - back to + and _ back to / before pasting URL-safe strings.

Padding errors are the #1 source of 'invalid Base64' bugs. A token of length 11 cannot decode — Base64 strings must be a multiple of 4. The fix is to append 1, 2, or 3 = until the length is a multiple of 4. Some tools silently accept unpadded input; some throw an error. If you see 'incorrect padding', add equals signs until the length divides by 4.

Line breaks in MIME Base64 (RFC 2045) come every 76 chars because old SMTP servers had line-length limits. Modern decoders strip line breaks before decoding, but some strict implementations do not. If you see decode errors on a Base64 blob from an email or PEM file, run a regex replace /\s/g first to collapse all whitespace, then decode.

Encoding does not encrypt. This is worth repeating because Base64 looks like ciphertext and even experienced developers occasionally treat it as obfuscation. Anyone with the Base64 string can recover the original bytes instantly. Never use Base64 to 'hide' API keys, passwords, or PII — it adds zero security. Use real encryption (AES-GCM, age, libsodium) for actual secrets, and treat Base64 purely as a binary-to-ASCII transport format.

**Q: Does it decode JWT tokens?**

Partly. A JWT is three Base64URL segments; paste the header or payload segment (after replacing - with + and _ with /, and adding = padding) and the decoder shows its JSON. It does not split the token or check the signature for you.

**Q: What is the maximum input size?**

There is no fixed limit; strings of several megabytes decode instantly. Decoded output is roughly 75 % of the encoded size since Base64 inflates content by about a third.

**Q: Can it detect images automatically?**

Yes. If the input is an image data URI, or the decoded bytes start with a PNG, JPG, GIF or WebP header, the tool shows a preview and a download button instead of text.

**Q: Is the input sent to a server?**

No. All decoding happens client-side using the browser's atob and TextDecoder APIs. ConverterUp does not have an endpoint that receives Base64 strings, which matters when the encoded data contains credentials.

**Q: Does the decoder verify JWT signatures?**

No. ConverterUp decodes Base64 but does not verify JWT signatures, which requires the signing key (HMAC secret or RSA/ECDSA public key). To verify, use the issuer's public key with a JWT library like jose (Node) or PyJWT (Python).

**Q: How do I decode Base64 that was encoded multiple times?**

Paste the output back into the decoder and decode again, repeating until you reach readable text. Double-encoding is a common pattern in legacy systems where two layers tried to 'be safe' independently.

### Case Converter — camelCase, snake_case, kebab-case

URL: https://converterup.com/tools/case-converter

Convert text case online between UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE. ConverterUp's case converter is a fast helper for developers renaming variables, copywriters cleaning headlines, and SEO specialists normalizing slugs. Paste your input, click the format you need, and copy the result with one tap. The text is processed entirely in your browser, so blog drafts, code snippets, and internal product names never leave your device.

#### Where each case is used

camelCase (userId, fetchUserData) is the JavaScript and TypeScript convention for variables and functions. It is also standard in Java, Swift, Kotlin, and most modern OO languages for local variables and methods.

snake_case (user_id, fetch_user_data) dominates Python (PEP 8), Ruby, Rust, and SQL. It is also the de-facto JSON convention for APIs designed against Python or Rails backends. Snake case wins on long identifiers because underscores create natural word breaks.

kebab-case (user-id, fetch-user-data) is the URL slug convention, the CSS class and custom-property convention, and the HTML attribute convention. It is invalid as an identifier in almost every programming language because the hyphen parses as subtraction.

PascalCase (UserId, FetchUserData) marks types and classes in most languages: classes in JavaScript/TypeScript/Python/Java/C#, structs in Rust and Go (exported only), components in React. CONSTANT_CASE (MAX_RETRIES) is universal for compile-time constants, environment variables, and configuration keys.

#### Language and framework conventions

Go uses case as visibility: identifiers starting with an uppercase letter are exported (public); lowercase are package-private. User and user are not just style choices — they change the language semantics. This is unique to Go among major languages.

Ruby uses snake_case for methods and variables, PascalCase for classes and modules, and SCREAMING_SNAKE for constants. Rust enforces the same conventions with compiler warnings: non_snake_case and non_upper_case_globals lints fire on style violations.

JSON conventions are not standardized but de-facto split by ecosystem: REST APIs from Python/Rails backends use snake_case keys; APIs from Node/Java backends use camelCase; some legacy Microsoft APIs use PascalCase. Keep a single convention per API and document it.

CSS uses kebab-case for properties (background-color), custom properties (--brand-primary), and class names by convention (.product-card, BEM .product-card__title--featured). HTML uses kebab-case for custom data attributes (data-user-id) but reserves camelCase for ARIA properties accessed in JavaScript (el.dataset.userId).

#### Programmatic gotchas: acronyms, numbers, transitions

Acronyms are the hardest part of case conversion. Should XMLHttpRequest become x_m_l_http_request or xml_http_request? Most modern style guides recommend the latter, and Google's JavaScript style guide says to treat acronyms as a single word in camelCase: parseHtml, not parseHTML. ConverterUp follows that convention: a run of capitals is treated as one word.

Numbers are also ambiguous. Does html5Parser split as html5 + Parser or html + 5Parser? ConverterUp keeps digits attached to the word they touch, so html5Parser becomes html5_parser in snake_case. Double-check identifiers with numbers in the middle before renaming code.

Word boundaries on already-mixed input are detected at lowercase-to-uppercase transitions (fooBar → foo, Bar), acronym-to-word transitions (HTMLParser → HTML, Parser), and explicit separators (hyphens, underscores and spaces). When converting a mix of conventions, paste once, normalize to a known intermediate (often kebab-case), then convert to the target.

**Q: How does Title Case differ from Sentence case?**

Title Case capitalizes the first letter of each significant word, like in book titles. Sentence case capitalizes only the first letter of the sentence and proper nouns, which is the standard for body copy.

**Q: Does case conversion preserve numbers and punctuation?**

Yes. Digits, punctuation, and emoji are kept untouched. The tool only changes letter casing and adjusts separators (underscore, hyphen, dot) when converting to programmer-friendly cases.

**Q: Does it handle Portuguese and Spanish accents correctly?**

Yes. The converter is fully Unicode-aware, so accented letters such as á, ã, ç, ñ, and ü keep their diacritics and convert their case correctly in either direction.

**Q: Is there a maximum text length?**

There is no fixed limit; even long documents convert instantly thanks to native browser string APIs.

**Q: How are acronyms like XML, HTTP, and ID handled?**

A run of capital letters is treated as one word: XMLHttpRequest becomes xmlHttpRequest in camelCase and xml_http_request in snake_case. There is no option to keep acronyms fully uppercase — adjust those by hand if your style guide requires it.

**Q: Can I convert a list of names line by line?**

UPPERCASE, lowercase, Title Case and Sentence case keep your line breaks, so they work on whole lists. The programmer cases (camelCase, snake_case, kebab-case, PascalCase, CONSTANT_CASE) join all the input into one identifier — convert one name at a time for those.

### CSV to JSON Converter — Free Online, No Upload

URL: https://converterup.com/tools/csv-to-json

Convert CSV to JSON online with support for custom delimiters, quoted fields, and an optional header row. ConverterUp's CSV to JSON converter is built for analysts importing spreadsheets into APIs, developers seeding databases, and product managers turning exports from Notion or Google Sheets into structured data. Paste a CSV or upload a file, pick the delimiter and header option, and download the resulting JSON array or copy it to the clipboard. Parsing runs in your browser, so customer lists and financial exports never leave your device.

#### CSV quirks: RFC 4180, quoting, BOM, encoding

RFC 4180 is the closest thing to a CSV spec, but most CSV files in the wild deviate from it. The canonical rules: comma separator, CRLF line endings, double quotes around fields containing commas or newlines, and a literal double quote inside a quoted field is escaped as two double quotes ("").

BOM (byte order mark, EF BB BF for UTF-8) is added by Excel when saving CSV with UTF-8 encoding, and it routinely breaks naive parsers — the first column name becomes \uFEFFid instead of id. If your first key looks odd in the JSON output, re-save the CSV as UTF-8 without BOM, or rename that key after converting.

Encoding: Excel on Windows often defaults to Windows-1252 or UTF-16 LE, not UTF-8. Saving a CSV with accented characters from Excel and importing into a UTF-8-only API is the classic source of João mojibake. Convert to UTF-8 with BOM in Excel via Save As → CSV UTF-8, or open the file in a real text editor to confirm the encoding before parsing.

Line endings vary: Windows tools produce \r\n, Unix tools \n. ConverterUp accepts both and skips empty lines, so files from any modern tool convert cleanly.

#### Header detection and nested JSON output

With headers enabled, the first row becomes the property names and each subsequent row is emitted as an object: [{"id":"1","name":"Ana"},…]. This is the standard format expected by most APIs. With headers disabled, each row is emitted as an array ([["1","Ana"],…]) — useful for positional data or when the CSV has no header line.

Column names are taken as written, trimmed of surrounding spaces. If you need camelCase or snake_case keys, run the header row through the case converter first.

Real CSV data is flat by nature; JSON consumers often want nested objects. ConverterUp produces flat objects — a column named address.city becomes the key "address.city" — so reshape nested structures in your code or with a tool like jq after converting.

Every value is output as a string, which preserves leading zeros (ZIP codes, phone numbers, SKUs) and avoids the JavaScript 0.1 + 0.2 float trap. Convert numbers, booleans and dates in your code once the data is loaded, where you know each column's real type.

#### Common conversion problems

Commas inside values: "Smith, John" must be wrapped in double quotes. If your source CSV has unquoted commas inside values (a frequent bug in hand-edited files and some legacy exports), every line will have a wrong column count — try the semicolon or tab delimiter, which many European exports use.

Line breaks inside cells: multi-line values (addresses, comments) are valid CSV when wrapped in double quotes, but ConverterUp reads the file line by line, so a line break inside a cell starts a new row. Replace in-cell line breaks with a space in your spreadsheet before exporting.

Unescaped quotes: a value containing a literal " must double it ("He said ""hi"""). Some exporters use backslash escaping ("He said \"hi\"") instead, which is invalid RFC 4180 — re-export with standard quoting if values come out split or wrong.

**Q: Which delimiters are supported?**

Comma, semicolon, tab, and a custom field where you can type any character (for example a pipe |). Pick the delimiter your file uses before converting.

**Q: How are quoted fields and escaped quotes handled?**

Fields wrapped in double quotes can contain the delimiter (for example "Smith, John"). Line breaks inside quoted cells are not supported — replace them with spaces before converting.

**Q: What is the maximum CSV size?**

There is no fixed limit; files with tens of thousands of rows convert in the browser in a moment. Very large files depend on your device's memory.

**Q: Can I get an array of objects instead of arrays?**

Yes. Enable the header option and the first row is used as JSON keys, producing an array of objects. Disable it to get an array of arrays, useful when the source has no header or you want positional access.

**Q: How are empty fields and missing values represented?**

An empty field becomes an empty string (""). A row with fewer columns than the header gets the missing keys set to "" as well, so every object has the same keys.

**Q: Why does Excel break my CSV when I save it back?**

Excel re-encodes to the system default (Windows-1252 on Windows in many locales), strips the UTF-8 BOM, and reformats numbers and dates aggressively — a leading zero in a ZIP code becomes 00501 → 501, an ISO date becomes a US date string. For round-tripping CSV through Excel safely, import via Data → From Text and explicitly set each column to Text.

### HEIC to JPG Converter — Free iPhone Photos, No Upload

URL: https://converterup.com/tools/heic-to-jpg

Convert HEIC photos to JPG, PNG, or WebP directly in your browser. ConverterUp's HEIC converter is built for iPhone and iPad owners who need to share or upload photos to apps and websites that do not yet accept Apple's HEIC format — Windows photo viewers, older versions of Photoshop, most CMS dashboards, and many email clients. Drop the .heic file, pick the target format, and download the converted image in seconds. The decode happens locally using a WebAssembly build of libheif, so the original photo never leaves your device or gets uploaded to a third-party server.

#### Why iPhones save HEIC instead of JPG

Since iOS 11 (2017), iPhones default to HEIC (High Efficiency Image Coding), an Apple-branded variant of the HEIF container. The reason is storage: HEIC compresses photos roughly 50 % smaller than JPG at the same visual quality, thanks to the modern HEVC codec underneath. A 12 MP iPhone photo lands at around 2 MB instead of 4 MB.

The catch is compatibility. Only Apple platforms and a handful of newer apps decode HEIC natively. Open the file on a Windows 10 PC, drop it into a Notion page, attach it to a Gmail message, or upload it to an older WordPress install, and you typically get a generic preview, an error, or nothing at all.

Converting HEIC to JPG (or PNG, WebP) restores universal compatibility. You lose the storage savings, but you gain the ability to share, embed, edit, and back up the photo anywhere — including services that have not updated their image pipeline for the past decade.

If you want to skip the conversion step entirely for future photos, open iPhone Settings → Camera → Formats and switch from High Efficiency to Most Compatible. The iPhone will save JPG directly. Existing HEIC photos in your library still need conversion.

#### JPG vs PNG vs WebP — which output to pick

JPG is the safe default. Every browser, OS, CMS, social network, and email client handles it. Use 90–95 % quality for visual results indistinguishable from the HEIC source, with a file size roughly 1.5–2× larger than the original. Pick JPG when you do not know where the photo will end up.

PNG is lossless — every pixel from the decoded HEIC is preserved exactly. Use it when you plan to edit the photo further, when the image contains text or graphics, or when you need transparency (rare for camera photos). File sizes are typically 5–10× larger than the HEIC source.

WebP at 90 % quality lands close to HEIC's size while being readable by every modern browser (Chrome, Firefox, Safari 14+, Edge). Pick it when the photo is destined for the web and you control the platform. For email attachments and offline sharing, stick with JPG — older clients still mishandle WebP.

All three outputs strip the HEIC's encoded HDR information down to standard sRGB / 8-bit. If you need to preserve HDR for professional editing, export from Photos.app on macOS with the original encoding intact instead — this tool optimizes for sharing, not archival.

#### Privacy, one photo at a time, and EXIF

ConverterUp's HEIC converter is 100 % client-side. The libheif WebAssembly binary (~1 MB) is loaded lazily from a public CDN on the first conversion, then cached by your browser. Your photos are decoded in memory and re-encoded by the browser's native canvas — at no point does any image data reach a ConverterUp server. Compare this to most online HEIC converters which require an upload.

EXIF metadata (camera model, GPS coordinates, capture date) is stripped during conversion by default, because canvas.toBlob does not preserve it. For most photo-sharing use cases this is the privacy-friendly default. If you specifically need to keep EXIF, edit the photo in Apple Photos before exporting as JPG/PNG instead.

The converter handles one photo at a time: drop a HEIC, download the result, then drop the next. For Live Photos (HEIC + paired MOV), the tool converts the still image only — the motion / audio track is part of the .MOV companion file and is not embedded in the HEIC. To combine several HEIC photos into one document, use HEIC to PDF, which accepts up to 20 files.

**Q: Why won't Windows open my iPhone HEIC photos?**

Windows 10 and 11 can open HEIC, but only after installing Microsoft's HEIF Image Extensions (free) AND HEVC Video Extensions (paid in some regions). If you don't want to pay or install extensions, convert HEIC to JPG once and view normally.

**Q: Is the converted JPG smaller or larger than the HEIC?**

Larger, typically 1.5–2× bigger at 92 % JPG quality. HEIC's HEVC codec is more efficient than JPG's DCT. If file size matters more than universal compatibility, choose WebP at 85–90 % — it stays close to the HEIC source size.

**Q: Are my photos uploaded to a server?**

No. Decoding runs in your browser via a WebAssembly build of libheif loaded from a CDN. The browser then re-encodes to JPG / PNG / WebP using its native canvas API. ConverterUp has no upload endpoint for image data and cannot see your photos.

**Q: What is the maximum file size?**

50 MB per file. A typical iPhone HEIC is 2–5 MB, so this covers everything from standard photos to high-resolution 48 MP iPhone Pro shots. Larger files may work but will be slow on low-end mobile devices because libheif runs single-threaded.

**Q: Does this work for HEIC Live Photos and burst shots?**

It converts the primary (first) image inside the HEIC container. Live Photos store the motion as a separate .MOV file that iOS pairs in the Photos library — that motion track is not inside the HEIC and is not converted. Burst HEICs typically contain a single representative frame.

**Q: Does the tool support HEIF and HEIC sequences?**

Yes. The .heif and .heic extensions are decoded by the same libheif pipeline. Multi-image HEIC sequences are detected, but the converter exports the first image only. If you need every frame from a sequence, an "export all frames" option is planned for a future release.

### HEIC to PDF Converter — Combine iPhone Photos to PDF

URL: https://converterup.com/tools/heic-to-pdf

Combine multiple iPhone HEIC photos into a single multi-page PDF, directly in your browser. ConverterUp's HEIC-to-PDF tool is built for anyone who has dozens of HEIC files from an iPhone and needs to share, print, or archive them as one document — receipts, ID scans, recipes, screenshots, or photo batches for clients. Drop the photos, choose A4 fit or native page size, and download a single PDF. The decode pipeline (libheif) and the PDF assembly (pdf-lib) both run client-side, so the originals never leave your device.

#### Why combine HEIC photos into a PDF

PDF is the universal portable document — every operating system, mail client, cloud drive, and printer reads it without extensions. Bundling 5–20 HEIC photos into one PDF beats sending them individually as image attachments, especially when the recipient is on Windows, an older Android, or a CMS that does not accept HEIC at all.

Typical use cases: receipts for expense reports (combine 10 receipt photos into one expense doc), ID scans for bank/visa applications (front + back as one file), recipes and notes photographed page by page, real estate listings bundled per property, and school assignments turned in as a single deliverable.

Compared to printing-and-scanning, a HEIC-to-PDF pipeline preserves the original image fidelity, takes seconds instead of minutes, and works from any phone with no hardware required. The output is also smaller and shareable by email or link straight away.

#### A4 fit vs native page size

A4 fit places each HEIC on a standard 595 × 842 pt page (A4 portrait or landscape, auto-rotated to match each photo's orientation), centered with margins. This is what you want for printable documents, contract attachments, school turn-ins, and anything destined for an inbox where the reader will likely print or sign.

Native sets each page to the photo's exact pixel dimensions in points (1 pixel = 1 point). The image fills the page edge-to-edge with no margin and no scaling. Pick this for digital-only archives, photo books, and any case where you do not want the PDF reader to add empty borders.

Both modes embed the JPG bytes verbatim — pdf-lib does not re-rasterize. The final PDF size is approximately the sum of JPG sizes (at your chosen quality) plus a few KB of structure. A 5-page PDF at 90 % quality from typical 4 MB HEICs lands around 4–8 MB.

#### Quality, limits, and privacy

The quality slider controls the JPG encoder before embedding. 90 % is a sweet spot — visually indistinguishable from the HEIC source for most photos, with a manageable PDF size. Drop to 75 % for email attachments where size beats fidelity. Push to 100 % for archive-grade copies (expect 3–5× larger files).

Hard caps are 20 files per PDF, 50 MB per file, and 200 MB total. The limits protect mobile Safari, which OOMs around 12 MP × 20 canvases. For more files, build two PDFs and merge with a separate PDF merger.

Privacy: the libheif WASM and pdf-lib JS are loaded from CDNs but every byte of your photos is processed in your browser. ConverterUp has no upload endpoint, no telemetry on file contents, and no server-side log of what you converted. The output PDF blob is created with URL.createObjectURL and lives only in your tab until you close it.

**Q: How many HEIC photos can I combine into one PDF?**

Up to 20 per PDF, with a 200 MB total cap. The limit exists because libheif runs single-threaded in WASM and mobile Safari OOMs around 12 MP × 20 canvases. For more, build two PDFs and merge them.

**Q: Can I reorder photos before building the PDF?**

Photos are added in the order they appear in your file picker or drop. To change the order, remove the photos you want later and add them again last.

**Q: Are my photos uploaded anywhere?**

No. Both the HEIC decode (libheif via WASM) and the PDF assembly (pdf-lib) run entirely in your browser. The output PDF is created in-memory and offered as a download via blob URL. ConverterUp has no upload endpoint for image data.

**Q: What page size does the PDF use?**

Two modes. A4 fit centers each photo on a standard A4 page (595 × 842 pt, auto-rotated portrait or landscape). Native matches each page to the photo's pixel dimensions exactly with no margin. Pick A4 for printing, native for digital archives.

**Q: Will the PDF be much larger than the HEIC files?**

Roughly equal to the sum of the JPG-encoded photos at your chosen quality. 5 × 4 MB HEIC at 90 % quality typically produces a 4–8 MB PDF. Quality 100 % doubles it; quality 75 % halves it. pdf-lib does not re-rasterize, so there is no compounding loss.

**Q: Does the PDF embed the original EXIF metadata?**

No. The decode-and-re-encode pipeline drops EXIF by the time the JPG hits the PDF. That is the privacy-friendly default — GPS coordinates and timestamps stay out of the document. If you need EXIF preserved, edit the HEIC in Apple Photos and export individual JPGs with metadata before merging.

## Format conversions

- [PNG to JPG](https://converterup.com/convert/png-to-jpg): convert PNG to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [JPG to PNG](https://converterup.com/convert/jpg-to-png): convert JPG to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [PNG to WebP](https://converterup.com/convert/png-to-webp): convert PNG to WebP in the browser (uses https://converterup.com/tools/media-converter).
- [JPG to WebP](https://converterup.com/convert/jpg-to-webp): convert JPG to WebP in the browser (uses https://converterup.com/tools/media-converter).
- [WebP to PNG](https://converterup.com/convert/webp-to-png): convert WebP to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [WebP to JPG](https://converterup.com/convert/webp-to-jpg): convert WebP to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [PNG to AVIF](https://converterup.com/convert/png-to-avif): convert PNG to AVIF in the browser (uses https://converterup.com/tools/media-converter).
- [JPG to AVIF](https://converterup.com/convert/jpg-to-avif): convert JPG to AVIF in the browser (uses https://converterup.com/tools/media-converter).
- [AVIF to JPG](https://converterup.com/convert/avif-to-jpg): convert AVIF to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [AVIF to PNG](https://converterup.com/convert/avif-to-png): convert AVIF to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [WebP to AVIF](https://converterup.com/convert/webp-to-avif): convert WebP to AVIF in the browser (uses https://converterup.com/tools/media-converter).
- [AVIF to WebP](https://converterup.com/convert/avif-to-webp): convert AVIF to WebP in the browser (uses https://converterup.com/tools/media-converter).
- [GIF to PNG](https://converterup.com/convert/gif-to-png): convert GIF to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [GIF to JPG](https://converterup.com/convert/gif-to-jpg): convert GIF to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [GIF to WebP](https://converterup.com/convert/gif-to-webp): convert GIF to WebP in the browser (uses https://converterup.com/tools/media-converter).
- [PNG to GIF](https://converterup.com/convert/png-to-gif): convert PNG to GIF in the browser (uses https://converterup.com/tools/media-converter).
- [JFIF to JPG](https://converterup.com/convert/jfif-to-jpg): convert JFIF to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [JFIF to PNG](https://converterup.com/convert/jfif-to-png): convert JFIF to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [BMP to PNG](https://converterup.com/convert/bmp-to-png): convert BMP to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [BMP to JPG](https://converterup.com/convert/bmp-to-jpg): convert BMP to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [BMP to WebP](https://converterup.com/convert/bmp-to-webp): convert BMP to WebP in the browser (uses https://converterup.com/tools/media-converter).
- [TIFF to JPG](https://converterup.com/convert/tiff-to-jpg): convert TIFF to JPG in the browser (uses https://converterup.com/tools/media-converter).
- [TIFF to PNG](https://converterup.com/convert/tiff-to-png): convert TIFF to PNG in the browser (uses https://converterup.com/tools/media-converter).
- [TIFF to WebP](https://converterup.com/convert/tiff-to-webp): convert TIFF to WebP in the browser (uses https://converterup.com/tools/media-converter).
- [PNG to ICO](https://converterup.com/convert/png-to-ico): convert PNG to ICO in the browser (uses https://converterup.com/tools/favicon-generator).
- [JPG to ICO](https://converterup.com/convert/jpg-to-ico): convert JPG to ICO in the browser (uses https://converterup.com/tools/favicon-generator).
- [SVG to ICO](https://converterup.com/convert/svg-to-ico): convert SVG to ICO in the browser (uses https://converterup.com/tools/favicon-generator).
- [SVG to WebP](https://converterup.com/convert/svg-to-webp): convert SVG to WebP in the browser (uses https://converterup.com/tools/svg-to-png).
- [HEIC to PDF](https://converterup.com/convert/heic-to-pdf): convert HEIC to PDF in the browser (uses https://converterup.com/tools/heic-to-pdf).
- [HEIC to AVIF](https://converterup.com/convert/heic-to-avif): convert HEIC to AVIF in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [HEIF to PNG](https://converterup.com/convert/heif-to-png): convert HEIF to PNG in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [HEIF to WebP](https://converterup.com/convert/heif-to-webp): convert HEIF to WebP in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [SVG to PNG](https://converterup.com/convert/svg-to-png): convert SVG to PNG in the browser (uses https://converterup.com/tools/svg-to-png).
- [SVG to JPG](https://converterup.com/convert/svg-to-jpg): convert SVG to JPG in the browser (uses https://converterup.com/tools/svg-to-png).
- [HEIC to JPG](https://converterup.com/convert/heic-to-jpg): convert HEIC to JPG in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [HEIC to PNG](https://converterup.com/convert/heic-to-png): convert HEIC to PNG in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [HEIC to WebP](https://converterup.com/convert/heic-to-webp): convert HEIC to WebP in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [HEIF to JPG](https://converterup.com/convert/heif-to-jpg): convert HEIF to JPG in the browser (uses https://converterup.com/tools/heic-to-jpg).
- [MP4 to GIF](https://converterup.com/convert/mp4-to-gif): convert MP4 to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [GIF to MP4](https://converterup.com/convert/gif-to-mp4): convert GIF to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [WebM to GIF](https://converterup.com/convert/webm-to-gif): convert WebM to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [MOV to GIF](https://converterup.com/convert/mov-to-gif): convert MOV to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [AVI to GIF](https://converterup.com/convert/avi-to-gif): convert AVI to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [MOV to MP4](https://converterup.com/convert/mov-to-mp4): convert MOV to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [WebM to MP4](https://converterup.com/convert/webm-to-mp4): convert WebM to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [AVI to MP4](https://converterup.com/convert/avi-to-mp4): convert AVI to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to WebM](https://converterup.com/convert/mp4-to-webm): convert MP4 to WebM in the browser (uses https://converterup.com/tools/media-converter).
- [MKV to MP4](https://converterup.com/convert/mkv-to-mp4): convert MKV to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [MKV to GIF](https://converterup.com/convert/mkv-to-gif): convert MKV to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [MKV to WebM](https://converterup.com/convert/mkv-to-webm): convert MKV to WebM in the browser (uses https://converterup.com/tools/media-converter).
- [FLV to MP4](https://converterup.com/convert/flv-to-mp4): convert FLV to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [FLV to GIF](https://converterup.com/convert/flv-to-gif): convert FLV to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [3GP to MP4](https://converterup.com/convert/3gp-to-mp4): convert 3GP to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [TS to MP4](https://converterup.com/convert/ts-to-mp4): convert TS to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [M4V to MP4](https://converterup.com/convert/m4v-to-mp4): convert M4V to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [M4V to GIF](https://converterup.com/convert/m4v-to-gif): convert M4V to GIF in the browser (uses https://converterup.com/tools/video-to-gif).
- [WMV to MP4](https://converterup.com/convert/wmv-to-mp4): convert WMV to MP4 in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to MOV](https://converterup.com/convert/mp4-to-mov): convert MP4 to MOV in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to AVI](https://converterup.com/convert/mp4-to-avi): convert MP4 to AVI in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to MKV](https://converterup.com/convert/mp4-to-mkv): convert MP4 to MKV in the browser (uses https://converterup.com/tools/media-converter).
- [WebM to MOV](https://converterup.com/convert/webm-to-mov): convert WebM to MOV in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to MP3](https://converterup.com/convert/mp4-to-mp3): convert MP4 to MP3 in the browser (uses https://converterup.com/tools/media-converter).
- [Video to MP3](https://converterup.com/convert/video-to-mp3): convert Video to MP3 in the browser (uses https://converterup.com/tools/media-converter).
- [MOV to MP3](https://converterup.com/convert/mov-to-mp3): convert MOV to MP3 in the browser (uses https://converterup.com/tools/media-converter).
- [WebM to MP3](https://converterup.com/convert/webm-to-mp3): convert WebM to MP3 in the browser (uses https://converterup.com/tools/media-converter).
- [MKV to MP3](https://converterup.com/convert/mkv-to-mp3): convert MKV to MP3 in the browser (uses https://converterup.com/tools/media-converter).
- [AVI to MP3](https://converterup.com/convert/avi-to-mp3): convert AVI to MP3 in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to WAV](https://converterup.com/convert/mp4-to-wav): convert MP4 to WAV in the browser (uses https://converterup.com/tools/media-converter).
- [MP4 to AAC](https://converterup.com/convert/mp4-to-aac): convert MP4 to AAC in the browser (uses https://converterup.com/tools/media-converter).
- [CSV to JSON](https://converterup.com/convert/csv-to-json): convert CSV to JSON in the browser (uses https://converterup.com/tools/csv-to-json).
- [VTT to SRT](https://converterup.com/convert/vtt-to-srt): convert VTT to SRT in the browser (uses https://converterup.com/tools/vtt-to-srt).
- [Image to Base64](https://converterup.com/convert/image-to-base64): convert Image to Base64 in the browser (uses https://converterup.com/tools/image-to-base64).
- [Base64 to Image](https://converterup.com/convert/base64-to-image): convert Base64 to Image in the browser (uses https://converterup.com/tools/base64-decode).
- [Hex to Decimal](https://converterup.com/convert/hex-to-decimal): convert Hex to Decimal in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Decimal to Hex](https://converterup.com/convert/decimal-to-hex): convert Decimal to Hex in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Binary to Decimal](https://converterup.com/convert/binary-to-decimal): convert Binary to Decimal in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Decimal to Binary](https://converterup.com/convert/decimal-to-binary): convert Decimal to Binary in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Decimal to Octal](https://converterup.com/convert/decimal-to-octal): convert Decimal to Octal in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Octal to Decimal](https://converterup.com/convert/octal-to-decimal): convert Octal to Decimal in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Hex to Binary](https://converterup.com/convert/hex-to-binary): convert Hex to Binary in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Binary to Hex](https://converterup.com/convert/binary-to-hex): convert Binary to Hex in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Hex to Octal](https://converterup.com/convert/hex-to-octal): convert Hex to Octal in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Octal to Hex](https://converterup.com/convert/octal-to-hex): convert Octal to Hex in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Binary to Octal](https://converterup.com/convert/binary-to-octal): convert Binary to Octal in the browser (uses https://converterup.com/tools/hex-to-decimal).
- [Octal to Binary](https://converterup.com/convert/octal-to-binary): convert Octal to Binary in the browser (uses https://converterup.com/tools/hex-to-decimal).

## Guides

- [How to Compress Images Without Losing Quality](https://converterup.com/blog/how-to-compress-images-without-losing-quality): Learn how to reduce image file sizes by up to 80% while keeping them sharp. Free browser-based compression with no uploads required.
- [How to Download Any YouTube Thumbnail in HD](https://converterup.com/blog/how-to-download-youtube-thumbnail): Download YouTube video thumbnails in all resolutions — from 120x90 to 1280x720 HD. Free online tool, instant download, no software or signup needed.
- [PNG vs JPG vs WebP: Which Format to Use When](https://converterup.com/blog/png-vs-jpg-vs-webp): PNG vs JPG vs WebP: lossy vs lossless, real size benchmarks, transparency, browser support, and which format to use for photos, graphics, and the web.
- [How to Convert MP4 to GIF Free Online](https://converterup.com/blog/how-to-convert-mp4-to-gif): Convert any MP4 video clip to an animated GIF directly in your browser. Control frame rate, size, and quality. No upload required.
- [What Is EXIF Data and Why You Should Remove It](https://converterup.com/blog/what-is-exif-data): EXIF data stores camera settings, GPS location, and more in your photos. Learn what it contains and how to strip it for privacy.
- [Stripe Fees 2026: How Much Does Stripe Charge?](https://converterup.com/blog/stripe-fees-explained): Stripe charges 2.9% + 30¢ in the US, 1.5% + 25¢ in EU, +1% international, +1% conversion. See exact rates, refund policy, and net payout calculator.
- [How to Create a QR Code with Custom Logo and Colors](https://converterup.com/blog/how-to-create-qr-code-with-logo): Generate branded QR codes with your logo in the center, custom colors, and high error correction. Free, no sign-up needed.
- [VTT vs SRT: Subtitle Formats Explained](https://converterup.com/blog/vtt-vs-srt-subtitles): Understand the differences between WebVTT and SRT subtitle formats, when to use each, and how to convert between them instantly.
- [How to Resize Images for Every Social Media Platform](https://converterup.com/blog/how-to-resize-images-for-social-media): The complete guide to image sizes for Instagram, Twitter, Facebook, LinkedIn, and more. Resize instantly in your browser.
- [How to Extract Frames from a Video as Images](https://converterup.com/blog/how-to-extract-frames-from-video): Capture individual frames from MP4, MOV, or WebM videos as PNG or JPG. Precise seek controls, custom intervals, and batch download as a ZIP file.
- [Image to Base64: What It Is and How to Use It](https://converterup.com/blog/image-to-base64-guide): Learn what Base64 encoding is, when to embed images as data URIs in HTML or CSS, and how to convert any JPG, PNG, or SVG to Base64 instantly.
- [How to Convert SVG to PNG (and When You Should)](https://converterup.com/blog/how-to-convert-svg-to-png): Convert SVG vector files to PNG raster images with custom scale and background. Understand when each format is the right choice.
- [How to Create a Favicon for Your Website](https://converterup.com/blog/how-to-create-favicon): Generate all favicon sizes from a single image — 16x16, 32x32, 180x180 Apple Touch, PWA icons — plus the HTML <link> code ready to paste.
- [How to Extract a Color Palette from Any Image](https://converterup.com/blog/how-to-extract-colors-from-image): Extract dominant colors from any photo or image. Get HEX, RGB, and HSL values for your design projects — perfect for palettes, branding, and UI mockups.
- [Hex to Decimal Conversion Explained](https://converterup.com/blog/hex-to-decimal-conversion): Understand hexadecimal numbers and how to convert between hex, decimal, binary, and octal. Includes color code conversion.
- [JSON Formatting and Validation: A Complete Guide](https://converterup.com/blog/json-formatting-validation-guide): Learn how to format, validate, and debug JSON data: syntax highlighting, prettify, minify, and fixes for the most common JSON parse errors.

## Optional

- [About](https://converterup.com/about): who builds ConverterUp and how it works.
- [Privacy policy](https://converterup.com/privacy)
- [Portuguese articles](https://converterup.com/pt/blog)
- [Spanish articles](https://converterup.com/es/blog)
- [Full text for LLMs](https://converterup.com/llms-full.txt)