Frequently Asked Questions

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

JPEG, PNG, and WebP are fully supported. The tool can also accept BMP and GIF inputs, converting them during compression.

The tool uses smart compression that minimizes visible quality loss. At 80% quality, most images look identical to the original while being 50-70% smaller. Use the slider to find your ideal balance.

There is no hard limit since processing happens in your browser. Files up to 50 MB work well on most devices. Very large files may be slower on mobile devices.

Yes — drop two or more images to activate batch mode. A quality slider applies to all files, each is processed sequentially in your browser, and you can download them individually or as a single ZIP file. No upload, no sign-up, no limit.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Lock the aspect ratio and change one dimension — the other adjusts automatically to prevent distortion.

There is no server limit since processing happens in your browser. Images up to 8000x8000 pixels work well on most devices. Performance depends on your device's memory.

You can scale up, but enlarging images beyond their original size will reduce quality. For best results, start with the highest resolution source image available.

The resized image is saved in the same format as the original (JPEG, PNG, or WebP). Use the Format Converter tool if you need a different format.

Yes. Drop 2 or more images to activate batch mode. All files are resized to the same dimensions using your width, height, and aspect ratio settings. Download them individually or all at once as a ZIP. Everything runs in your browser — no upload required.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

You can convert between PNG, JPEG, and WebP in any direction. All three formats are fully supported as both input and output.

Converting to JPEG or WebP uses lossy compression by default, which may slightly reduce quality. Converting to PNG is always lossless. Use the quality setting when converting to JPEG or WebP to control the trade-off.

JPEG does not support transparency, so transparent areas are filled with a solid color (usually white) during conversion. If you need to preserve transparency, convert to PNG or WebP instead.

It depends on the target format. Converting PNG to JPEG or WebP will typically reduce file size. Converting JPEG to PNG may increase file size because PNG is lossless. For explicit size reduction, use the Image Compressor after converting.

Yes. Drop 2 or more images onto the tool to activate batch mode. All files are converted to the same target format using your quality setting. Download them individually or all at once as a ZIP archive. Everything runs in your browser — no upload required.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Base64-encoded images can be embedded directly in code, eliminating extra HTTP requests. This is particularly valuable for email templates (which block external images), single-file HTML documents, and API payloads that need to transport image data as text.

Yes. Base64 encoding increases the data size by approximately 33% because it represents binary data using only ASCII characters. For this reason, it is best suited for small images (under 5 KB). Larger images are more efficiently served as separate files.

PNG, JPEG, WebP, GIF, and SVG are all supported. The MIME type in the data URI is set automatically based on the file type.

Yes. Use the dev/base64 tool to decode a Base64 string, or paste the data URI directly into a browser address bar to view the image.

Yes. Drop 2 or more images to activate batch mode. All files are encoded instantly in your browser. Click 'Download all as JSON' to get a structured JSON file containing the data URI, Base64 string, and HTML img tag for every image — no upload required.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The tool uses a pre-trained ONNX segmentation model that runs directly in your browser via WebAssembly. It identifies the subject in your image and creates a precise mask to remove the background. No data is sent to any server.

The AI model (~5 MB) is downloaded once from a CDN and cached in your browser. Subsequent uses load instantly from cache. This keeps the initial page load fast while still providing powerful AI capabilities.

The AI works best with portraits, product photos, pets, and objects with clear outlines. Complex scenes with multiple overlapping subjects may produce less precise results.

No hard limit since processing happens in your browser. Images up to 20 MP work well on desktop. Very large images may be slower on mobile devices.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

PNG, JPEG, WebP, and GIF are all supported. Any format your browser can display will work.

The tool uses the median cut algorithm — a well-known color quantization technique. It analyzes all pixels in the image, recursively splits them along the color channel with the widest range, and averages each group to find the most representative colors.

Yes. You can copy individual colors (hex, RGB, or HSL), copy all colors at once, or download a 1200x630 PNG image showing your source image alongside the extracted color bars — perfect for social media sharing.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

EXIF (Exchangeable Image File Format) metadata can include GPS coordinates, camera make and model, camera serial number, lens information, exposure settings, date and time, software used to process the image, and sometimes the photographer's name or copyright notice.

No. This tool strips only the metadata bytes from the file. The image pixel data is completely untouched, so there is no quality loss whatsoever.

JPEG and PNG are supported. These are the two most common formats that carry EXIF metadata. WebP and HEIC are not currently supported.

Major platforms like Facebook, Instagram, and Twitter do strip EXIF on upload. However, many smaller platforms, messaging apps, and direct file transfers do not. It is safer to strip metadata before sharing rather than relying on the platform.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Any image format your browser can display works — this includes JPEG, PNG, WebP, and GIF. The cropped output is downloaded as a PNG to preserve quality.

Yes. You can enter exact pixel dimensions for the crop area. The tool displays the current selection dimensions in real time as you drag.

Cropping itself does not reduce quality — you are simply selecting a subset of the original pixels. The output is a full-quality PNG at the cropped dimensions.

No hard limit — processing happens in your browser. Very large images (20 MP+) may take a moment to load on mobile devices.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

You can export SVG to PNG (supports transparency), JPG (smaller file size, no transparency), and WebP (modern format with good compression and transparency support).

Yes. You can specify any width and height in pixels for the output image. The SVG will be rendered at that exact resolution, making it suitable for retina displays or specific platform requirements.

SVGs can reference external fonts or resources that may not load during conversion. Ensure your SVG is self-contained (fonts embedded, no external image links) for the most accurate rendering.

Basic raster-to-SVG conversion is supported, which wraps the raster image in an SVG container. For full vectorization (tracing), a dedicated vector tracing tool is recommended.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Currently English is supported. Tesseract supports over 100 languages — additional language packs may be added in future updates.

The OCR engine requires a trained language model (~10 MB for English). This is downloaded once from the jsDelivr CDN and stored in your browser's IndexedDB cache. After the first download, the tool works instantly and even offline.

Tesseract produces excellent results on clearly typed, high-contrast text. Accuracy drops with handwriting, decorative fonts, low resolution, skewed scans, or noisy backgrounds. For best results, use a straight, well-lit photo with dark text on a light background.

No hard limit — processing happens entirely in your browser. Large images (10 MB+) may take longer on mobile devices, but there is no server-imposed cap.

Not directly — this tool works with image files (JPEG, PNG, WebP). To extract text from a PDF, use the PDF to Image tool first to convert a page to an image, then run OCR.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

JPEG, PNG, and WebP. The output format matches your input — JPEG in, JPEG out.

Currently only text watermarks are supported. Image overlay support may be added in a future update.

No. The watermark is drawn directly onto a full-resolution canvas. JPEG and WebP exports use 92% quality, which is virtually lossless for most uses.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

There is no hard limit. Performance depends on your browser and device memory. Most users can merge dozens of PDFs without issues.

Basic document structure is preserved. Complex bookmarks, form fields, and JavaScript actions may not carry over, as the merge focuses on page content.

Password-protected PDFs must be unlocked before merging. The tool cannot process encrypted files directly.

Yes. The tool works on any modern mobile browser. Tap to select files from your device and merge them just like on desktop.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Enter individual page numbers or ranges separated by commas. For example: 1,3,5-8 extracts pages 1, 3, 5, 6, 7, and 8. You can mix single pages and ranges freely.

Password-protected PDFs must be unlocked before splitting. The tool cannot process encrypted files directly — open the PDF in your PDF viewer first to unlock it.

Yes. Page content including text, images, and vector graphics is preserved. Complex interactive features like form fields, JavaScript, and certain annotations may not carry over.

There is no hard limit. Performance depends on your device's memory and the size of the PDF. Most users can split PDFs with hundreds of pages without issues.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Drop two or more PDFs onto the tool to activate batch mode. Each PDF is compressed independently, and you can download them all in a single ZIP archive.

No. Text and vector graphics remain sharp regardless of the compression level. Only embedded raster images (photos, screenshots) are recompressed, which is where most PDF file size comes from.

It depends on the content. PDFs with lots of high-resolution embedded images can shrink by 50-80%. PDFs that are mostly text may only reduce by 5-15%, since text is already stored very efficiently.

The PDF must be unlocked before compression. Open it in your PDF viewer, remove the password protection, then upload it to compress.

This typically means the PDF is already well-optimized, or its content is mostly text and vector graphics rather than images. Try the PDF Splitter to remove unnecessary pages, which is another way to reduce file size.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

No. Rotation only changes how pages are displayed. All text, links, and form fields remain fully intact and searchable.

Yes. Use the page range input to specify exactly which pages to rotate (e.g., '1, 3-5, 8').

You can rotate pages by 90° clockwise, 180° (upside down), or 90° counter-clockwise (270°).

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Set the 'Start Number' to any value. For example, set it to 3 if your first two pages are a cover and table of contents.

Yes. The tool detects page rotation and adjusts the position of page numbers accordingly so they always appear in the correct orientation.

Page numbers are rendered in Helvetica, a clean and universally compatible font embedded directly in the PDF.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Use the opacity slider to set transparency from 0% (invisible) to 100% (fully opaque). The default 30% is subtle enough to read through.

The watermark is drawn directly on the PDF pages. It will appear when viewing, printing, or sharing the document. However, it can be removed by someone with PDF editing software.

Currently, the watermark is applied to all pages. For selective watermarking, consider splitting the PDF first, watermarking the desired pages, then merging them back.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Drop two or more PDFs to activate batch mode. Each PDF is converted independently and you can expand each item to preview its pages. Download all images from all PDFs in a single ZIP.

Resolution depends on the scale factor. At 2x scale, a standard A4 page produces an image around 1190×1684 pixels. Use 3x for print-quality output.

Use PNG for text-heavy documents or when you need lossless quality. Use JPG for photo-heavy PDFs or when file size matters more than perfect quality.

Currently, all pages are converted. You can download only the pages you need from the preview grid.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Toggle to 'Each image → separate PDF' mode at the top of the tool. Each image becomes its own PDF document, and you can download them all in a ZIP archive.

JPG/JPEG, PNG, and WebP are supported. WebP images are automatically converted to PNG before embedding in the PDF.

There is no hard limit. However, very large numbers of high-resolution images may be slower on mobile devices due to memory constraints.

Yes. Choose 'Fit to Image' to make each page match the image dimensions, or select A4 or Letter to scale images within standard page sizes.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Accuracy depends on the quality of the original scan. Clean, high-contrast scans with standard fonts typically achieve 95%+ accuracy. Handwritten text, low-contrast scans, or unusual fonts will produce lower accuracy.

Currently English only. Support for additional languages may be added in future updates.

Type "all" to process every page, "1-3" for a range, "1,3,5" for specific pages, or combinations like "1-3,7,9-11".

Password-protected PDFs cannot be read without the password. Open the PDF in your PDF viewer, remove or disable the password protection, then try again.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Words are split by whitespace. Hyphenated words (e.g., 'well-known') count as one word. Numbers, abbreviations, and contractions each count as one word. Empty lines between paragraphs do not affect the word count.

No. The counter works with any length of text, limited only by your browser's memory. You can paste an entire book if you want.

Both counts are shown: characters with spaces and characters without spaces. This is useful because different platforms define 'characters' differently.

Reading time is estimated based on an average adult reading speed of around 200-250 words per minute. For technical or complex text, actual reading time will be longer.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

camelCase, PascalCase, snake_case, kebab-case, UPPER CASE, lower case, Title Case, and Sentence case are all supported.

Yes. Paste any amount of text and click the case button. The entire text is converted, preserving spaces, line breaks, and punctuation.

When converting from camelCase or PascalCase to another format, the converter splits on uppercase letter boundaries. For example, 'myVariableName' splits into 'my', 'variable', 'name' before reassembling in the target format.

Acronyms in all caps (e.g., 'API', 'URL') are treated as single words in most conversion modes. This matches the convention used by most style guides and linters.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. The diff tool works with any plain text including source code, configuration files, JSON, YAML, HTML, Markdown, and CSV. Paste the file contents directly into each panel.

Added lines are highlighted in green, removed lines in red. Lines that exist in both versions but are unchanged are shown without highlighting. This follows the standard unified diff convention.

Yes. The comparison runs entirely in your browser and can handle thousands of lines. Performance scales with the number of changes, not the total document size.

Currently the tool requires pasting text. To compare file contents, open the file in a text editor, select all, and paste into the panel.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

By default sorting is case-insensitive, so 'Apple' and 'apple' sort to the same position. You can toggle case-sensitive mode if you need 'A' to come before 'a'.

Numeric sort treats each line as a number and sorts by value rather than alphabetically. This ensures '10' comes after '9' rather than between '1' and '2'.

Yes. When deduplication is enabled, the first occurrence of each unique line is kept and subsequent duplicates are removed. Sort order is then applied after deduplication.

The line sorter treats each line as a unit. For column-based CSV sorting, use the JSON-CSV Converter to work with the data as structured fields.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Tables, task lists, strikethrough, fenced code blocks with syntax highlighting, and autolinks are all supported as per the GitHub Flavored Markdown specification.

Yes. Click the Copy HTML button to copy the full rendered HTML markup. Paste it directly into any CMS, email template, or web page.

The tool implements GitHub Flavored Markdown. Platform-specific extensions like Hugo shortcodes, Jekyll front matter, or Notion-specific syntax will not render — they are specific to each platform's Markdown processor.

Math notation (LaTeX) is not currently supported. For math-heavy documents, tools like Overleaf or Typora with the KaTeX plugin are better suited.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The tool supports standard and GitHub-flavored Markdown including headings, bold, italic, links, images, tables, code blocks with syntax highlighting, blockquotes, horizontal rules, and nested lists.

Yes. You can choose from A4, US Letter, or Legal page sizes using the dropdown in the options panel.

Once the page is loaded, the tool works entirely in your browser and does not require an internet connection to generate PDFs.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Formatting adds whitespace and indentation to make JSON readable. Validating checks whether the JSON syntax is correct according to the RFC 8259 specification. Use the JSON Validator to check for syntax errors.

Yes. The formatter processes JSON of any size directly in your browser. Files up to 10 MB format instantly on most devices.

2-space indentation by default, which is the most common style in web development. You can change it to 4 spaces or tabs.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Common issues: trailing commas after the last item in arrays or objects, single-quoted strings instead of double-quoted, unquoted keys, comments (not allowed in JSON), and missing closing brackets or braces.

No. This tool validates strict JSON (RFC 8259). JSON5 and JSONC (JSON with Comments) are extensions that are not standard JSON. Use a dedicated JSON5 parser for those formats.

Yes. Validation happens entirely in your browser and works for files of any size.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

No. Minification only removes whitespace (spaces, tabs, newlines). The data structure and values are completely unchanged. Any JSON parser will produce identical results from both the formatted and minified versions.

Typically 20–40% depending on how much whitespace the original has. Heavily indented JSON with long keys benefits most. Already-compact JSON will see smaller gains.

No. The tool validates your JSON first. If there are syntax errors, they are reported before minification so you can fix them.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

UTF-8 encoding is used by default, which supports all Unicode characters including emoji, accented letters, and non-Latin scripts.

Base64 output must be a length that is a multiple of 4, so '=' padding characters are added at the end when the input length is not divisible by 3. This is standard and expected — '==' means 2 padding bytes were needed, '=' means 1.

Base64url replaces '+' with '-' and '/' with '_', and omits the '=' padding. It is used in JWTs and URL parameters to avoid characters that have special meaning in URLs. This tool handles standard Base64; manually replace the characters if you are working with Base64url.

This tool is designed for text (UTF-8) input. For binary files like images, use the Image to Base64 tool which handles binary data correctly via the FileReader API.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

No. This tool decodes and displays JWT contents only. Signature verification requires the signing secret (for HMAC) or the public key (for RSA/ECDSA), which the tool deliberately does not accept to avoid handling sensitive credentials.

Yes. The token is decoded entirely in your browser using JavaScript and is never sent to any server. However, as a general security practice, revoke and rotate tokens that may have been exposed, even if you trust the tool.

'alg: none' means the JWT has no signature and should be rejected by any properly configured server. If you see this in a production token, it indicates a critical security misconfiguration.

JWT timestamps (exp, iat, nbf) are in Unix seconds, not milliseconds. The decoded date is shown in UTC — your local timezone offset may make it appear different from what you expect.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

JavaScript's built-in RegExp engine is used. This supports most standard regex features including lookahead, lookbehind, named capture groups, and Unicode property escapes (with the 'u' flag). Patterns tested here will behave identically in any browser-side JavaScript and in Node.js.

Greedy quantifiers (*, +, ?) match as much as possible. Try their lazy equivalents (*?, +?, ??) to match the minimum. Also check whether the 's' flag is inadvertently enabled, causing '.' to match newlines.

All standard JavaScript flags: g (global — find all matches), i (case-insensitive), m (multiline — ^ and $ match at line boundaries), s (dotAll — '.' matches newlines), u (Unicode mode), and y (sticky — match only at current position).

The tester uses JavaScript's RegExp engine. Most PCRE features (used by Python, PHP, Ruby, and Perl) are also available in JavaScript, but there are some differences — most notably, Python's verbose mode (?x) and atomic groups are not available in JavaScript.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

SHA-256 and SHA-512 are considered cryptographically secure for data integrity verification. SHA-1 is provided for compatibility with legacy systems but is not recommended for new security-critical use — meaningful collision attacks have been demonstrated against SHA-1.

No. Raw SHA-256 is not suitable for password storage because it is too fast — an attacker can try billions of guesses per second. Use slow, purpose-built password hashing functions like bcrypt, Argon2, or scrypt instead.

This is the avalanche effect — a core property of cryptographic hash functions. Even a 1-bit change in input flips roughly half the output bits on average. This makes hashes useful for detecting any modification to data.

This tool hashes text input. To hash an entire binary file, you would need a command-line tool (sha256sum on Linux/Mac) or a file hashing tool. Text files can be pasted here if their contents are readable plain text.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

All characters except unreserved characters (A-Z, a-z, 0-9, -, _, ., ~) are percent-encoded per RFC 3986. This includes spaces (%20), ampersands (%26), equals signs (%3D), and forward slashes (%2F).

%20 is the RFC 3986 standard encoding for a space. The '+' encoding is specific to application/x-www-form-urlencoded (HTML form submissions). Both mean 'space', but %20 is safer and more universally understood in URL contexts.

%25 is the encoding for a literal '%' character. If your input contained a '%', it was encoded to %25. Be careful not to double-encode already-encoded URLs, which would turn %20 into %2520.

You can paste either. To encode an entire URL correctly (preserving path slashes and query structure), use encodeURI mode. To encode a single query parameter value, use encodeURIComponent mode which encodes more characters including '/' and '?'.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

All standard HTML5 named entities (&, <, >,  , ©, and hundreds more), all decimal numeric entities (&), and all hexadecimal entities (&) are supported.

Always encode user-supplied content before inserting it into HTML to prevent XSS attacks. Also encode when embedding code examples in web pages, so the browser displays < and > as characters rather than interpreting them as HTML tags.

Named entities (&amp;amp;) are human-readable but require browser support for the name. Numeric entities (&amp;#38;) work in any HTML context and are safer for email templates where client support varies. Both represent the same character.

Encoding characters inside attribute values and text nodes is safe. Do not encode characters that are structural HTML syntax — for example, do not encode the < and > in actual HTML tags or the = in attribute assignments.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. They are generated using the Web Crypto API (crypto.randomUUID or crypto.getRandomValues), which provides cryptographically secure randomness. These UUIDs are safe to use as secure identifiers, unlike UUIDs generated with Math.random() which are not cryptographically strong.

Both tools generate the same standard UUID v4 format. The dev/uuid page is presented in the developer tools section with a focus on API integration, bulk generation, and developer workflows. The generate/uuid page targets general users who need a quick one-off UUID.

In theory yes, but in practice no. The probability of generating a duplicate UUID is approximately 1 in 2^122 — about 1 in 5 undecillion. You would need to generate billions of UUIDs per second for millions of years before expecting a collision.

UUID v4 is completely random, which can cause index fragmentation in B-tree databases like PostgreSQL. UUID v7 (time-ordered) is better for database primary keys because it maintains insertion order. Use v4 for general unique identifiers and v7 for database row IDs when performance matters.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since January 1, 1970 00:00:00 UTC, also called the Unix epoch. It is the most common way to represent dates in programming and databases because it is timezone-agnostic and easy to do arithmetic on.

Timestamps with 13 digits are in milliseconds, which is what JavaScript's Date.now() returns. Timestamps with 10 digits are in seconds, which is the standard POSIX/Unix format used by most other languages and systems. Toggle the precision setting accordingly.

In 32-bit systems, Unix timestamps overflow on January 19, 2038 (the Y2K38 problem). JavaScript uses 64-bit floating point, so Date can represent dates far beyond that — up to approximately year 275,760.

Yes. When converting a timestamp to local time, JavaScript's Date object automatically applies your system's DST rules. Timestamps are always stored in UTC internally, so the conversion is unambiguous.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Binary (base 2), octal (base 8), decimal (base 10), and hexadecimal (base 16) — the four bases most commonly used in programming and computer science.

Hexadecimal is compact and maps cleanly to binary — each hex digit represents exactly 4 binary bits (a nibble), and two hex digits represent one byte. This makes memory addresses, color codes, and binary data much more readable than long binary strings.

'0x' is a conventional prefix in most programming languages (C, Python, JavaScript, Java) that tells the compiler or interpreter the following digits are hexadecimal. It has no mathematical meaning — 0xFF and FF both equal 255 in decimal.

This tool converts unsigned non-negative integers. Negative numbers require two's complement representation, which is base-specific and depends on word size (8-bit, 16-bit, 32-bit, etc.). For signed binary arithmetic, a dedicated two's complement tool is more appropriate.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

All major languages are supported including JavaScript, Python, TypeScript, Go, Rust, Java, C++, HTML, CSS, SQL, and many more.

Yes. Choose from multiple built-in themes and adjust the background color and padding to match your needs.

Images are exported at 2x resolution for crisp display on high-DPI screens and print materials.

No hard limit, but for best results keep snippets under 30 lines. Very long code blocks become unreadable as images.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Minification removes whitespace and comments without changing functionality. However, edge cases exist — always test the minified output before deploying to production.

Typically 20-60% smaller depending on how much whitespace and comments the original contains. Heavily commented code benefits the most.

Currently the tool supports plain HTML, CSS, and JavaScript. TypeScript and SCSS should be compiled first, then the output can be minified.

No. Minification reduces file size by removing unnecessary characters. Compression (like gzip) is a separate step done by your web server. Both work together for maximum size reduction.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Syntax highlighting supports JavaScript, TypeScript, Python, Java, Go, Rust, C/C++, HTML, CSS, JSON, YAML, SQL, and many more.

The Code Diff tool adds syntax highlighting and is optimized for source code. The Text Diff tool is better for plain text comparisons like documents or logs.

Yes. Paste or type any amount of code in both panels. The tool handles files of any size, though very large files may be slower on mobile devices.

The tool performs a line-by-line diff. Lines that are moved will show as deleted from the old position and added at the new position.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Linear (directional), radial (circular/elliptical from a center point), and conic (color transitions around a center point, like a color wheel).

There is no practical limit. You need at least 2 stops, and you can add as many as you want for complex multi-color gradients.

Yes. CSS gradients are supported in all modern browsers including Chrome, Firefox, Safari, and Edge. No vendor prefixes needed.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Click 'Add Shadow' to add additional shadow layers. Multiple shadows are comma-separated in the CSS output.

An inset shadow appears inside the element rather than outside, creating an inner shadow effect often used for pressed buttons or input fields.

Yes. The opacity slider controls the alpha channel of the shadow color, outputting proper rgba() values.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

backdrop-filter is supported in Chrome, Edge, Safari, and Firefox 103+. The generated CSS includes the -webkit- prefix for Safari. Older browsers will show a semi-transparent background without the blur.

The saturate() filter increases color vibrancy of the background content visible through the glass. Values above 100% make colors more vivid, enhancing the frosted glass effect.

Glassmorphism works best on colorful or image backgrounds. On solid white or dark backgrounds, the blur effect is less noticeable since there is less visual content to blur.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

justify-content controls spacing along the main axis (horizontal for row, vertical for column). align-items controls alignment along the cross axis (perpendicular to main axis).

Use flexbox for one-dimensional layouts (a row or a column). Use CSS Grid for two-dimensional layouts (rows AND columns). Flexbox is better for distributing space among items in a single direction.

flex-basis sets the initial size of a flex item before flex-grow and flex-shrink are applied. Common values include 'auto' (use the item's content/width), specific lengths like '200px', or percentages like '50%'.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The 'fr' unit represents a fraction of the available space in the grid container. '1fr 2fr' creates two columns where the second is twice as wide as the first.

Yes. You can combine fr, px, %, auto, and other CSS units. For example, '250px 1fr' creates a fixed sidebar and a flexible main column.

Use CSS Grid for two-dimensional layouts (controlling both rows and columns). Use Flexbox for one-dimensional layouts (a single row or column). Grid is ideal for page-level layout, while Flexbox excels at component-level alignment.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. clip-path with basic shapes and polygons is supported in all modern browsers. For the widest compatibility, the tool generates standard clip-path without vendor prefixes.

Yes, if both shapes have the same number of polygon points. CSS transitions and animations can smoothly morph between clip-path values. Generate keyframe values using different presets with the same point count.

This tool uses percentage values, which makes the clip-path responsive — it scales with the element's size. You can also use other CSS units in your code if needed.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Names, emails, usernames, phone numbers, addresses, URLs, IPs, UUIDs, booleans, integers, floats, dates, hex colors, lorem ipsum text, company names, product names, and prices. Template Mode also supports parameterized tokens for custom ranges.

A seed is a string that makes generation deterministic — the same seed always produces the same data. This is useful for reproducible tests, sharing data scenarios with teammates, and debugging.

Yes! Switch to Template Mode and write a JSON object with {{placeholder}} tokens. For example: {"name": "{{fullName}}", "age": {{integer(18,65)}}}. The tool will generate an array of objects matching your schema.

JSON array, CSV (with header row), SQL INSERT statements (with configurable table name), and TypeScript (interface definition + typed const array).

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Standard 5-field cron format: minute (0-59), hour (0-23), day of month (1-31), month (1-12), day of week (0-6, Sunday=0). Extended formats like seconds or years are not supported.

Run times are computed entirely in your browser using your local timezone. The tool iterates forward from the current time to find matching minutes.

Currently this supports standard 5-field cron only. Vixie cron shortcuts like @hourly or @daily are not supported yet.

The formatter handles standard SQL syntax including PostgreSQL, MySQL, SQLite, and SQL Server constructs. It gracefully handles unknown syntax by preserving it as-is.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The formatter focuses on formatting, not validation. It will format syntactically incomplete or incorrect SQL as best it can without throwing errors.

Yes. Separate statements with semicolons and each will be formatted independently with a blank line between them.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. The formatter validates well-formedness: all tags must be properly closed, attributes must be quoted, and there must be a single root element. It does not validate against an XSD schema — it checks structural correctness, not business rules.

XML is a strict data format where every tag must be closed and attribute values must be quoted. HTML is more lenient. XML is used for data exchange and configuration; HTML is for rendering content in browsers.

Yes, for reasonably sized files. Very large XML documents (multi-MB) may take a moment to process. For files over 10 MB, consider a desktop XML editor for better performance.

SOAP (Simple Object Access Protocol) is a messaging protocol used by many enterprise and legacy web services. It uses XML as its message format because XML is platform-neutral, extensible, and has strong tooling support across programming languages.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Comma (,), semicolon (;), tab (\t), and pipe (|) delimiters are supported. Semicolons are common in European CSV exports where commas are used as decimal separators.

No hard limit. The viewer handles files with tens of thousands of rows in most modern browsers. Very large files (100k+ rows) may be slower to render.

Yes. CSV fields that contain the delimiter character are typically enclosed in double quotes (per RFC 4180). The parser correctly handles quoted fields with embedded commas, newlines, and escaped quotes.

The viewer is read-only. To edit CSV data, use the CSV-to-JSON converter or copy the data into a spreadsheet tool.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. The converter uses the IANA timezone database built into modern browsers, which contains the complete history and future schedule of DST transitions for every region worldwide.

UTC (Coordinated Universal Time) is the primary time standard worldwide. It never observes daylight saving time and is the basis for all other timezones expressed as UTC offsets (e.g., UTC+9 for Japan Standard Time).

Many countries near the equator, where sunrise and sunset times are relatively constant year-round, do not observe DST. Major non-DST regions include most of Asia, Africa, and South America. The EU voted to abolish DST but has not yet implemented the change.

A UTC offset (+05:30, -08:00) is a fixed difference from UTC. A timezone (e.g., America/New_York) is a named region that follows specific DST rules — the UTC offset for a timezone changes throughout the year during DST transitions.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

HEX (e.g. #FF5733 or #F57), RGB (e.g. rgb(255, 87, 51)), and HSL (e.g. hsl(11, 100%, 60%)) are all supported as both input and output.

The converter currently handles opaque colors (no alpha channel). For transparency, use rgba() or hsla() in CSS, adjusting the alpha value manually. 8-digit HEX with alpha (#RRGGBBAA) is not currently supported as input.

They represent the same information differently. HEX encodes each of the three color channels (red, green, blue) as a two-digit hexadecimal number. RGB expresses the same values as decimal integers from 0 to 255. #FF5733 and rgb(255, 87, 51) are the exact same color.

HSL separates the color's properties into Hue (which color, 0-360°), Saturation (how vivid, 0-100%), and Lightness (how light or dark, 0-100%). This makes it easy to create variations — for example, keeping the same hue but generating lighter and darker shades by only changing the L value.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. Nested objects are flattened using dot notation when converting to CSV. For example, {user: {name: 'Alice', age: 30}} becomes two columns: user.name and user.age. Very deeply nested structures may produce many columns.

The input must be a JSON array of objects — for example, [{id: 1, name: 'Alice'}, {id: 2, name: 'Bob'}]. Each object in the array becomes one CSV row. JSON objects that are not arrays, or arrays of primitives, will not convert cleanly.

Arrays within JSON objects (e.g. tags: ['a', 'b', 'c']) are joined into a comma-separated string within a single CSV cell. This is the standard approach since CSV cannot represent nested arrays natively.

The tool supports configurable delimiters. Comma is the default, but you can switch to semicolon (common in European locales where commas are used as decimal separators) or tab-separated values.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The converter handles single-document YAML files. For multi-document files separated by --- delimiters, convert each document individually by splitting them manually.

No. JSON does not have a comment syntax, so YAML comments are discarded during conversion. Keep your YAML as the source of truth if comments are important.

The js-yaml parser supports YAML 1.2, which is the current specification. It is also backward-compatible with YAML 1.1 for most common constructs.

In YAML 1.1, unquoted values like yes, no, on, off are interpreted as booleans. If you intend the literal string 'yes', quote it in YAML: 'yes' or "yes". YAML 1.2 removed this behavior, but many parsers still apply it for compatibility.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Conversions use standard, scientifically defined conversion factors and are accurate to at least 10 decimal places for most units. SI base units are exact by definition; derived units use the highest-precision ratios available.

Temperature scales (Celsius, Fahrenheit, Kelvin) have different zero points, so conversion requires a formula rather than a simple multiplication. °C = (°F - 32) × 5/9 and K = °C + 273.15.

No. Several units share the same name but differ in value. A UK (imperial) pint is 568 mL; a US pint is 473 mL. A UK gallon is 4.55 L; a US gallon is 3.79 L. The tool specifies which system each unit belongs to.

Currency conversion is not included because exchange rates change constantly. This tool focuses on fixed physical unit conversions. Use a dedicated currency converter for exchange rates.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The calculator counts complete calendar years, then the remaining complete months, then the remaining days. It accounts for varying month lengths and leap years to give an accurate result.

In non-leap years, the tool treats March 1 as the equivalent birthday for calculation purposes, which is the most common convention.

Yes. Use the target date field to calculate what your age will be on any future date, or what someone's age was on a historical date.

No. The calculation is performed entirely in your browser's JavaScript engine. No data is transmitted or stored.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The calculator computes the exact calendar difference: first counting complete years, then complete months, then remaining days. This mirrors how people intuitively think about time spans.

Yes. Toggle the 'Business days only' option to exclude Saturdays and Sundays from the count. This is useful for calculating working days in a project or contract.

Yes. The tool handles any valid dates in the Gregorian calendar, including dates hundreds of years apart. Useful for historical research and genealogy.

By default, the count includes the start date but not the end date. This matches how most scheduling and project management tools work.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Three core calculation types: (1) What is X% of Y? (e.g., 15% of 200 = 30), (2) X is what percentage of Y? (e.g., 30 is what % of 200 = 15%), and (3) What is the percentage change from X to Y? (e.g., 200 to 230 = 15% increase).

Percentage change = ((New Value - Old Value) / Old Value) × 100. A positive result indicates an increase; a negative result indicates a decrease.

Yes. Enter the original (higher) value as the starting number and the new (lower) value as the ending number. The result will be a negative percentage indicating the decrease.

A percentage point is the arithmetic difference between two percentages. If interest rates rise from 2% to 5%, that is a 3 percentage point increase, but a 150% relative increase. These are different measures and are often confused in financial reporting.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

BMI (Body Mass Index) is a measure of body weight relative to height. The formula is: BMI = weight (kg) / height (m)². In imperial units: BMI = (weight (lb) / height (in)²) × 703. The result is a dimensionless number that is categorized into ranges.

According to the WHO: Underweight = below 18.5, Normal weight = 18.5–24.9, Overweight = 25–29.9, Obese = 30 and above. These are guidelines for adults 18 and older.

BMI is a population-level screening tool with known limitations. It can overestimate body fat in muscular individuals (like athletes) and underestimate it in older adults who have lost muscle mass. It also does not account for fat distribution, which affects health risk.

The tool calculates your healthy weight range based on the Normal weight BMI range (18.5–24.9) for your specific height. This gives you a concrete weight goal rather than just a category label.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. The countdown and Pomodoro timers use setInterval which continues to tick in the background. The stopwatch uses timestamps rather than frame counting, so it also stays accurate when the tab is not visible.

Browsers block audio until the user interacts with the page. Click the Start button — this grants audio permission and the beep will play on that session and all subsequent ones.

Yes. Open the Settings panel in the Pomodoro tab to set custom work, short break, and long break durations in minutes (1–120 minutes each).

The Pomodoro Technique is a time-management method developed by Francesco Cirillo. It breaks work into focused intervals (traditionally 25 minutes) separated by short breaks. After four intervals, you take a longer break. The structured rhythm helps maintain focus and avoid burnout.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

An amortization schedule is a complete table of every loan payment, showing exactly how much of each payment goes to interest and how much reduces the principal balance. Early payments are heavily weighted toward interest; later payments pay down more principal.

Because interest is calculated on the remaining balance, which decreases with each payment. As your balance falls, less interest accrues, so more of each fixed payment goes toward principal — a process called amortization.

Yes. Enter the home price minus your down payment as the loan amount, your mortgage rate as the annual rate, and 30 or 15 years as the term. The calculator gives you the principal and interest portion of your payment. Note that actual mortgage payments also include property tax, insurance, and possibly PMI, which this calculator does not include.

With a 0% interest rate the calculator correctly computes equal principal-only payments by dividing the loan amount by the number of months, resulting in no interest charges over the life of the loan.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

For a lump sum: A = P × (1 + r/n)^(n×t), where P is principal, r is annual rate, n is compounding frequency per year, and t is years. For regular contributions an additional future-value-of-annuity term is added: PMT × ((1 + r/n)^(n×t) − 1) / (r/n), where PMT is the per-period contribution.

Use the frequency that matches your actual account. Most savings accounts compound daily or monthly; many investment accounts and bonds use annual or quarterly compounding. Check your account agreement or ask your provider if you are unsure.

Monthly contributions are annualized to match the selected compounding period and added using the future value of an annuity formula. This correctly accounts for contributions that themselves earn compound interest over the remaining time.

No. The calculator shows pre-tax growth. In taxable accounts, interest and investment gains are typically subject to income or capital gains taxes each year, which would reduce the actual balance. Tax-advantaged accounts like 401(k)s and IRAs defer or eliminate this tax drag.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Any text, URL, email address, phone number, or Wi-Fi credentials. The QR code can store up to about 4,000 characters of text or roughly 7,000 numeric digits.

Yes. Generated QR codes are free to use for any purpose, including commercial use. There are no licensing restrictions.

No. The QR code itself is just an encoded image — it never expires. However, if it encodes a URL, the QR code only works as long as that URL is live.

For reliable scanning, print QR codes at least 2cm x 2cm (about 0.8 inches). For scanning from a distance (posters, banners), make them larger — roughly 1/10th the expected scanning distance.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Most modern phones support WiFi QR codes natively. iPhones with iOS 11+ and Android phones with Android 10+ can scan them directly with the built-in camera app. Older phones may need a QR scanner app.

WPA/WPA2/WPA3 (most common, recommended), WEP (legacy), and None (open networks). Select the type that matches your router's security settings.

Check the 'Hidden network' option. This tells the phone to try connecting even if the network doesn't broadcast its name.

No — the password is encoded in the QR code at generation time. You'll need to generate a new QR code if you change your WiFi password.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Passwords are generated using the Web Crypto API (crypto.getRandomValues), which provides cryptographically secure randomness. This is the gold standard for random number generation in browsers.

Use at least 16 characters with a mix of uppercase, lowercase, numbers, and symbols. Never reuse passwords across accounts. A 16-character password with all character types has over 10^30 possible combinations.

No. Passwords exist only in your browser's memory until you close or refresh the page. Nothing is saved, logged, or transmitted.

Yes. The tool works on any modern mobile browser. Tap generate, then copy the password to use it in your mobile apps.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Lorem Ipsum is scrambled Latin text derived from Cicero's philosophical work 'De Finibus Bonorum et Malorum' (45 BC). It has been the standard placeholder text in typesetting and graphic design since the 1500s. Its scrambled, Latin-like appearance gives a realistic sense of text density without being readable or distracting.

Yes. Lorem Ipsum is in the public domain and can be used freely for any purpose, commercial or otherwise. It is universally used as placeholder text in professional design work.

A standard Lorem Ipsum paragraph contains approximately 50-80 words. The canonical Lorem Ipsum begins with 'Lorem ipsum dolor sit amet...' and is derived from sections 1.10.32 and 1.10.33 of Cicero's text.

Lorem Ipsum is ideal for demonstrating typography and layout. However, for user testing or stakeholder presentations, consider using realistic content that matches the actual subject matter — it helps reviewers give more meaningful feedback on the design.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

UUID v4 is a 128-bit identifier generated entirely from random numbers. The format is xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx — 32 hexadecimal digits in five groups. The '4' indicates version 4 (random), and the y digit is constrained to 8, 9, a, or b to indicate the variant.

In practice, no. The probability of generating a duplicate UUID v4 is approximately 1 in 2^122. You would need to generate roughly 2.71 quintillion UUIDs before having a 50% chance of a single collision. For any realistic usage volume, collisions are not a concern.

Both tools generate the same standard UUID v4 format with the same cryptographic quality. The generate/uuid page is presented for general users who need a quick UUID. The dev/uuid page is in the developer section and emphasizes bulk generation, API integration context, and technical details about the generation process.

A UUID v4 has 122 bits of randomness, which is cryptographically strong. However, UUIDs are not designed for use as secrets — they follow a recognizable format that reduces their effective entropy slightly and makes them easier to guess than a fully random 128-bit token. For security tokens, use a purpose-built random token generator.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Yes. The generator follows the BIP-39 standard exactly: cryptographic entropy, SHA-256 checksum, and the official 2048-word English wordlist.

All BIP-39 compatible wallets including MetaMask, Ledger, Trezor, Trust Wallet, Phantom, and most modern cryptocurrency wallets.

12 words (128-bit entropy) is secure for most uses. 24 words (256-bit entropy) provides extra security for very high-value wallets. Both are considered safe by current standards.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The private key is multiplied on the secp256k1 curve to get the public key. The public key is hashed with keccak-256, and the last 20 bytes become the Ethereum address, formatted with an EIP-55 checksum.

Yes. You can import the private key into MetaMask or any Ethereum wallet. However, for real funds, consider generating keys on an offline device.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

EIP-55 is a checksum standard for Ethereum addresses. It encodes a checksum into the capitalization of the hex characters, allowing wallets to detect typos without changing the address format.

No. Lowercase addresses are valid but lack checksum protection. Converting to EIP-55 format adds error detection without changing the address itself.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

PNG, JPG, SVG, and WebP. SVG inputs produce the sharpest results since they're resolution-independent.

At minimum, include 16x16, 32x32, and the ICO file. For full platform coverage, also add 180x180 (Apple) and 192x192 + 512x512 (Android/PWA).

ICO is the traditional favicon format that bundles multiple sizes into a single file. It provides the widest browser compatibility, especially with older browsers.

Strongly recommended. Non-square images will be scaled to fit square dimensions, which may cause distortion. Crop your image to a 1:1 ratio before uploading for best results.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

USD, EUR, GBP, JPY, CAD, AUD, CNY, INR, BRL, and KRW are available in the currency selector. The symbol is used in both the preview and the PDF.

Yes. Click Upload Logo and select a PNG, JPG, or WebP image. The logo appears in the top-left corner of the invoice, both in the live preview and the downloaded PDF.

Invoice mode shows a due date and payment terms, intended for requesting payment. Receipt mode hides the due date and adds a green PAID stamp, intended as proof that payment has been received.

Yes. Click the + Add Item button to add as many line items as you need. Each item has its own description, quantity, and unit price. The PDF handles page overflow automatically if you have many items.

No. Since everything runs in your browser, there are no usage limits, no daily caps, and no watermarks on the output.

The tool does not store data between sessions. To keep a record, download the PDF after each invoice. For recurring invoices, you can keep the browser tab open and adjust the details as needed.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

No. It only generates a visual preview in your browser. Nothing is shared, uploaded to social platforms, or sent to any server. You can safely preview before your page is live.

Yes. Use the upload button to select an image from your device. It is previewed locally using a Base64 data URI — no upload to any server occurs.

Social platforms cache Open Graph metadata, sometimes for 24 hours or more. After updating your meta tags, use the platform's official tools (Facebook Sharing Debugger, Twitter Card Validator) to force a cache refresh and see the updated card.

The recommended size for Twitter, Facebook, and LinkedIn is 1200x630px (1.91:1 aspect ratio). This renders sharply on all device sizes and in all card types. Minimum sizes vary by platform and card type.

Yes. Paste any public URL and click Analyze — the tool fetches the page server-side to read its Open Graph and Twitter Card meta tags, then populates all fields automatically. This bypasses CORS restrictions that would prevent direct browser fetching. No data from the page is stored.

The quality score rates your Open Graph implementation out of 100 points across seven criteria: presence of og:title, og:description, og:image, and twitter:card, plus title length (≤60 chars), description length (≤200 chars), and HTTPS image URL. Failing items show specific tips for how to fix them.

Twitter/X, Facebook, LinkedIn, Discord, WhatsApp, and Slack. Each tab shows a platform-accurate card mockup matching that platform's real layout and styling.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Paste the generated tags inside the <head> section of your HTML page, before the closing </head> tag. In WordPress, use a plugin like Yoast SEO or RankMath to add them via the admin interface without editing HTML directly.

Open Graph (og:) tags are a standard created by Facebook and are used by most platforms including Facebook, LinkedIn, Slack, Discord, and WhatsApp. Twitter Card (twitter:) tags are specific to Twitter/X. When both are present, Twitter uses its own tags and other platforms use Open Graph. Twitter also falls back to og: tags if twitter: tags are absent.

Open Graph tags do not directly affect Google search rankings, but they improve the appearance of your links when shared on social media, which can increase click-through rates and drive more traffic to your site.

Use 'website' for homepages and static pages, 'article' for blog posts and news content (which enables additional article-specific properties), and 'product' for e-commerce product pages. The type helps platforms understand your content and may affect how they display the card.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The tool uses center-crop: your image is scaled so the shortest dimension fits the target size, then the excess on the longer dimension is trimmed equally from both sides. This preserves the center of the image, which is usually the most important part.

Twitter/X, Facebook, Instagram, LinkedIn, YouTube, and Pinterest — with presets for posts, cover photos, profile pictures, stories, and thumbnails for each platform.

Scaling an image to larger dimensions than its original size (upscaling) reduces quality and can produce a blurry result. For best results, start with an image at least as large as the target dimensions.

Each platform displays images differently in different contexts. A profile photo may appear as a square in some places and a circle in others. Instagram automatically crops posts that are not the expected ratio. This tool ensures your image starts at the correct dimensions, giving you the most control over how it appears.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

Gross margin measures the percentage of revenue remaining after subtracting only the product cost: (selling price - cost price) / selling price. Net margin accounts for all costs including marketplace fees, shipping, and advertising: (selling price - total costs) / selling price. Net margin gives a more accurate picture of actual profitability.

The presets use common default rates: Amazon 15%, eBay 13.25%, Etsy 6.5% + $0.20 per listing, and Shopify 2.9% + $0.30 per transaction. Actual rates vary by product category, seller tier, and region. Use the Custom option to enter your exact fee structure.

ROI (Return on Investment) is calculated as (profit per unit / cost price) x 100%. It tells you how much profit you earn relative to the amount you invested in the product. An ROI of 100% means you doubled your investment.

Break-even units per month = monthly fixed costs / profit per unit. This tells you the minimum number of units you must sell each month to cover fixed expenses like rent, subscriptions, and software. If profit per unit is zero or negative, break-even cannot be calculated.

Yes. Enter your service delivery cost as the cost price, your service fee as the selling price, and set shipping to zero. The margin and ROI calculations work the same way for service-based businesses.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

A SKU (Stock Keeping Unit) is a unique alphanumeric code that identifies a specific product variant in your inventory. SKUs make it faster to look up products, track stock levels, fulfill orders, and analyze sales by product. Unlike barcodes (which are machine-readable), SKUs are designed to be human-readable and meaningful.

Code 128 is one of the most widely used barcode symbologies for non-retail applications. It is supported by virtually all handheld barcode scanners, phone camera scanners, and warehouse automation systems. If your scanner reads barcodes, it almost certainly supports Code 128.

No. This tool generates Code 128 barcodes, which are used for internal inventory, shipping labels, and warehouse operations. Retail point-of-sale systems require UPC-A or EAN-13 barcodes, which use a different encoding and require a registered GS1 company prefix.

Code 128 can encode strings of any practical length, but longer SKUs produce wider barcodes that may not fit on small labels. A typical SKU of 15-25 characters works well on standard label sizes. The tool limits individual component lengths to keep SKUs reasonable.

The tool provides common presets for category prefixes (APP, CLO, ELE, etc.) and color codes (BLK, WHT, RED, etc.). The brand code field accepts any 2-4 character code you define. For fully custom SKU formats, you can generate a base set here and modify them in your spreadsheet or inventory system.

Yes. All processing happens entirely in your browser. Your data never leaves your device and is never uploaded to any server.

The PDF is formatted for A4 paper (210mm x 297mm), which is the international standard. The layout also prints correctly on US Letter paper (8.5 x 11 inches) due to the generous margins.

No. You can add as many items as needed. When items exceed one page, the PDF automatically adds additional pages with proper formatting.

The current version uses a clean text-based layout without logo support. Your business name appears prominently in the sender section. Logo support may be added in a future update.

Packing slips intentionally exclude pricing information — they serve as a shipment contents checklist, not an invoice. For a document that includes pricing, use the Invoice Generator tool instead.

Click 'Download PDF' to save the file, then open it in any PDF viewer (Preview on Mac, Adobe Reader on Windows, or your browser's built-in viewer) and print it. For best results, set your printer to 'Actual Size' rather than 'Fit to Page'.