Practical Tool Guides

Prepare an Image for a Website

Start with the original image. Repeatedly saving an already compressed JPEG can introduce blocky edges and muddy text. Keep a separate working copy so you can change your export later.

1. Choose the final dimensions. Check the layout where the image will appear. A 600-pixel-wide slot may benefit from a 1,200-pixel export on a high-density display, but uploading a full camera-resolution photograph wastes bandwidth when that detail will never be shown. Preserve the aspect ratio unless you intend to crop.
2. Choose a suitable format. Use the Advanced Image Converter. Compare JPEG or WebP for photographs. Use PNG when you need lossless edges or transparency supported by the destination. JPEG has no transparency, so choose a deliberate background color before converting a transparent logo.
3. Compare the actual output. Inspect faces, small letters, smooth gradients and high-contrast edges at the intended display size. Lower quality until artifacts appear, then step back. The smallest file is not always the most readable file.
4. Check embedded information. Use the EXIF Viewer to inspect supported camera metadata. A photo may include GPS coordinates. If needed, run the Image Metadata Remover, then inspect the exported copy again.
5. Upload and check the page. Give the file a descriptive name. In your website editor, add useful alternative text for informative images and set width and height to reserve layout space. Check the result on a phone as well as a desktop.

Common mistake: increasing a small image’s dimensions does not restore detail that was never in the source. If it looks soft at the required size, use a better original or display it smaller.

Convert Captions Without Losing the Message

Caption conversion changes the file format. It does not automatically transcribe a recording, verify every spoken word or decide where every sentence should end. Start with a transcript you can compare against the recording.

1. Keep the source. Save the original SRT, WebVTT or other supported caption file before opening the Subtitle Converter & Caption File Maker. Work on a copy when changing timing or text.
2. Check the beginning, middle and end. Compare cue times with the recording. A constant offset throughout the file usually needs a timing shift. An offset that grows over time may indicate a frame-rate or speed mismatch; moving all cues by the same amount will not solve it.
3. Review cue warnings. Look for overlaps, zero-length cues and reading speeds that make long captions difficult to follow. Preserve names, speaker changes and meaningful sound descriptions. Do not rely on spellcheck alone for proper names or technical terms.
4. Choose the destination format. SRT is widely used for uploads; WebVTT is designed for web text tracks. Formatting and positioning features are not interchangeable across every format. Review the exported file in the actual player.
5. Test with sound off. This exposes missing context, unclear speaker changes and captions that disappear before they can be read. Check mobile display so lines do not obscure important on-screen information.

Common mistake: renaming a file from .srt to .vtt does not convert its syntax. Use an actual conversion, and retain a plain-text transcript separately if you need an accessible reading copy.

Choose the Right PDF Conversion

First decide what you need from the PDF: its words, its appearance or an editable document. Those are different outputs, and choosing the wrong one is a common cause of disappointing conversions.

• For searchable words: try PDF to Text. If the document is made of scanned page images, a normal text extractor may return little or nothing. Optical character recognition is a separate step and requires proofreading.
• For visual page copies: use PDF to Images. Choose enough resolution for the destination. A page image preserves appearance but is not a substitute for selectable text or an accessible document.
• For editing: use the relevant converter in the PDF Tools directory. Complex columns, tables, embedded fonts and scanned pages may not reconstruct exactly. Compare the output with the original before sharing it.

Always keep the original when a file contains signatures, form fields, bookmarks or accessibility tags. Rebuilding a PDF can change or remove those features. A signature drawn as an image is different from a cryptographically signed document, and exporting a modified copy can invalidate the latter.

Before sending a converted file, open it in a second viewer, check page count and order, inspect the first and last pages, and search for a distinctive phrase. If the file is private, also review the tool’s processing and sharing instructions. BrowserTools’ local tools process documents on your device; explicitly using an external service or sharing feature changes where information travels.

Plan a Network Before Installing Equipment

Start with a device list: wired clients, wireless clients, cameras, access points and AV endpoints. Record each device’s bandwidth, power requirements and network segment. These tools calculate a plan from your inputs; they do not scan your network or measure its real-world performance.

1. Size the address space. Use the IP Subnet Calculator. For example, 192.168.10.0/24 spans .0 through .255; a conventional IPv4 LAN uses .1 through .254 for hosts. Reserve the gateway and other infrastructure addresses rather than assigning the entire range to clients.
2. Document assignments. The IP Address Schedule & VLAN Table Generator records device addresses, excluded ranges and VLAN assignments. Compare the plan against the router’s DHCP scope and existing reservations. A VLAN number in a worksheet does not configure switch isolation or firewall rules.
3. Budget throughput. Use the AVoIP Bandwidth Planner for video flows or the Audio Network Calculator for audio flows. Include simultaneous traffic, overhead, uplinks and redundancy; a switch’s advertised total capacity is not the same as every port’s usable throughput.
4. Budget power separately. The PoE Budget Calculator checks device loads, ports and switch power. Confirm both per-port compatibility and the shared power budget against manufacturer specifications.
5. Validate the installation. Use the Wi-Fi Coverage Planner as a starting estimate, then perform an on-site survey and tests with representative clients. Walls, interference and placement change coverage. Compare actual file-copy performance with the File Transfer Calculator to identify the expected slowest link.

Scope: these are planning tools, not live DNS, ping, traceroute, packet capture or speed-test services. Never treat an estimate as proof of security, coverage or service availability. Avoid publishing network diagrams, passwords or private address inventories.

Build and Rehearse a Show Rundown

Turn a production outline or spreadsheet into a timed running order that a host and control room can follow.

1. Start with the schedule, not the stopwatch. Set the show title and start time. Give every segment a clear title, a responsible presenter, a source and a realistic duration. Keep cues such as “roll video” or “stand by camera two” in the notes. The start time of each row is calculated from the durations above it; editing an early item moves everything after it.
2. Import an existing plan carefully. Choose Import CSV / Excel and upload CSV, TSV or a modern .xlsx workbook. Select the correct worksheet and header row. Map Item/Title, Type, Color, Talent, Source, Duration and Notes. Review the preview before appending or replacing. Numeric durations can mean seconds, minutes or Excel time fractions; select the interpretation that matches the source. Clock strings use MM:SS or H:MM:SS.
3. Build a useful visual language. Select a type and color before adding an item, or customize a row afterward. Use custom names such as Demo, Q&A or Awards when the standard list is not enough. Keep the written type label: color alone is not reliable for every operator or printed copy.
4. Rehearse, then run. Start Live Mode and use Next when the actual segment changes. Completed cues turn gray. Select an earlier item number to return to that cue and restart its countdown. This is operator-controlled; reaching zero does not automatically advance the show. Use a script rehearsal to adjust durations before the live event.

Worked Example

A 30-second opening, 90-second welcome and 6-minute interview total 8 minutes. With a 19:00 show start, the interview begins at 19:02. Importing a numeric 0.00416667 as Excel time gives approximately 6 minutes; importing it as seconds does not.

Before You Finish

• Compare total duration against your available slot, including breaks and transitions.
• Export and reimport a small sample before moving a large production spreadsheet. Check custom labels, colors, notes and duration units.
• Keep a printed or downloaded running order if the device, battery or browser fails.

Limits and Privacy

Imports are limited to 500 items, 5 MB files and a bounded workbook extraction size. Legacy binary .xls needs to be saved as .xlsx or CSV first. BrowserTools HTML .xls exports can be reopened. Excel formulas are not recalculated; imports use stored cell values. Live timing does not control playout equipment.

Rundowns and imported spreadsheets stay on this device. Browser-local storage is not team synchronization; export files to share or back up a plan.

Prepare a Character for a Tabletop Session

Keep character creation, at-the-table actions and backups distinct so you can find the right information quickly.

1. Enter the character your table actually uses. Use Character for identity, class labels, level and campaign rules. In Abilities & Skills, enter scores and choose saving-throw and skill proficiencies. Standard Array and the 4d6 option are starting methods, not character-creation approval. Confirm your edition, allowed sources and table rules with the game organizer.
2. Fill in combat and spell information. Set maximum/current HP, temporary HP, armor class, speed and initiative adjustments from your sheet. Add attacks with their to-hit bonus and dice notation. Enter spell slot maxima and prepared spells manually. Changing a class label or level does not automatically grant features, spells or extra HP.
3. Use Session while playing. The Session dashboard brings health, quick checks, prepared spells and attacks together. Add Resources & Charges for limited-use abilities or consumables. Assign each a manual, short-rest or long-rest recovery rule. Rest & Recovery previews which resource counters will reset; HP and spell-slot recovery require your explicit choices.
4. Protect your campaign history. Save Character creates a named local library entry. Export JSON is the editable portable backup; Print PDF is a reading/printing snapshot. Duplicate creates a separate draft for a level-up experiment. Undo/Redo reverses recent edits. If a session is interrupted, a recoverable draft may be available the next time you open the tool.

Worked Example

A character with 10 current HP and 4 temporary HP takes 6 damage. The tool removes the 4 temporary HP first, leaving 8 current HP. A Strength score of 15 gives a +2 ability modifier; a level-5 character has a +3 proficiency bonus, applied only where selected.

Before You Finish

• Check proficiency and expertise against your source sheet rather than enabling every skill.
• Roll a known attack and confirm the bonus and dice notation before using shortcuts during play.
• After importing a backup, confirm identity, HP, resources, spell slots and inventory, then save it as a library entry.

Limits and Privacy

This is an independent manual worksheet, not a complete character-legality engine, paid rulebook library or virtual tabletop. Concentration, exhaustion and conditions are reminders; penalties are not automatically applied. Recovery varies by class and table. The library holds up to 50 saved characters.

Characters, recoverable drafts and inventory are saved locally. Clearing browser data removes them. PDF is not an editable backup; keep JSON copies outside browser storage.

Plan a Room Before Moving Furniture

Use measured footprints to compare arrangements, then check real clearances in the room.

1. Measure the usable space. Enter the inside room dimensions, not the exterior building measurements. Choose centimeters or feet before editing. Record alcoves, fixed cabinetry, radiators, doors and windows separately; the planner currently models one rectangular room, not structural walls.
2. Replace preset dimensions. Furniture presets are convenient starting sizes. Measure the actual piece, including handles, projecting legs or a chair in use. Add a clear name to each footprint so exported plans are understandable without the editor.
3. Compare arrangements. Drag furniture with snapping, use the inspector for exact coordinates and rotate in 90-degree steps. Keyboard arrows move the selected piece; the displayed instructions explain the finer increment. Undo and redo let you test an arrangement without rebuilding the room.
4. Check beyond the drawing. Review overlap and out-of-bounds warnings. A rug under a desk may overlap intentionally; a cabinet across a doorway does not become safe because the rectangles fit. Mark the proposed arrangement with tape and check doors, drawers, walking paths and access to outlets.

Worked Example

A 500 × 400 cm room has 20 square meters of floor area. A 140 × 70 cm desk occupies 0.98 square meters, but that does not include the chair or the clearance needed to sit down and move around it.

Before You Finish

• Confirm that feet and centimeters were not mixed during entry.
• Measure every purchased item rather than relying on preset or catalog thumbnail proportions.
• Keep a JSON plan for editing and a labeled PDF or PNG for discussion.

Limits and Privacy

One rectangular room, up to 100 rectangular furniture footprints and right-angle rotation. Door swings, irregular walls, building regulations, accessibility and structural engineering are not validated. Area calculations alone are not ordering advice for materials.

Plans stay in local browser storage unless you export or share them. Avoid publishing a detailed private home layout with sensitive personal information.

Clean Up Text Without Changing Its Meaning

Separate formatting changes from editorial decisions, and verify the final destination’s requirements.

1. Keep a clean source copy. Paste into a working copy before changing capitalization, line breaks or duplicate lines. Names, product codes and deliberately repeated quotations can be meaningful. A cleanup operation cannot infer why the original writer used them.
2. Apply one operation at a time. Convert case first if that is the requirement, then handle whitespace and duplicates separately. Preview a short sample containing acronyms, apostrophes and proper names. Automated title case may need editorial corrections for your organization’s style.
3. Measure the correct output. Word and character limits are different. Count the submission body separately from references, captions or titles if the destination asks for that. Hyphenated text, emoji and scripts without spaces may be counted differently across applications.
4. Compare and submit. Use a text comparison to check what changed. Read the beginning and end and search for important names or identifiers. Finally paste into the destination editor and check its own count and formatting.

Worked Example

“NASA launches the API” should not necessarily become “Nasa Launches The Api.” Case conversion changes letters; it does not know your preferred acronym style. Review such terms after conversion.

Before You Finish

• Check whether duplicate matching should be case-sensitive.
• Preserve meaningful blank lines in poems, addresses and code.
• Recheck the final form’s count after pasting; its rules may differ.

Limits and Privacy

These tools do not verify factual accuracy, authorship, spelling in every language or publication-specific style. A word count is not an LLM token count.

Local text tools process in the browser. Copying results into a cloud editor, email or chat creates a separate copy subject to that service’s policies.

Prepare JSON and Spreadsheet Data for Handoff

Preserve data types, identifiers and boundaries while moving between human-readable and structured formats.

1. Identify the shape. Decide whether the data is a list of records, a nested object or a table with headers. A flat spreadsheet cannot express every nested relationship without an agreed convention. Keep the original before flattening arrays or objects.
2. Validate a small representative sample. Use JSON formatting to find syntax mistakes such as trailing commas or single-quoted keys. Include rows with commas inside quoted fields, embedded newlines, blank cells and non-English characters when testing CSV conversion.
3. Protect identifiers and dates. Treat account numbers, postal codes and long IDs as text if their exact representation matters. Converting 00123 to a number loses its leading zeros. A spreadsheet may reinterpret a date-looking string using local settings; confirm the desired format with the recipient.
4. Test the real import. Open the exported file in the destination, check row counts and column mappings, and inspect edge cases. Valid JSON syntax does not prove that the receiving application accepts the schema or the values.

Worked Example

A CSV field containing “Smith, Ada” must be quoted so the comma does not start another column. An ID such as “000042” should remain a string if the six-digit representation is required.

Before You Finish

• Compare record counts before and after conversion.
• Check duplicate column names, empty values, line endings and UTF-8 characters.
• Do not run formulas from untrusted spreadsheet content. Review values beginning with formula-like characters before opening them in a spreadsheet.

Limits and Privacy

Formats differ in how they represent types, nesting and missing values. JavaScript numbers have precision limits; large identifiers should remain quoted strings. Conversion is not schema validation.

These conversions are local. Remove credentials and personal information before exporting samples into issue trackers or support messages.

Build and Reuse a Color Palette

Capture a color, refine a gradient and keep editable values separate from a screenshot.

1. Choose a trustworthy source. Sample the original artwork where possible. A compressed screenshot may add edge colors that are not part of the intended design. Sample broad flat areas rather than anti-aliased lettering or the edge of a shadow.
2. Use the right picker mode. The screen eyedropper depends on browser support and requires an explicit user action. If it is unavailable, import an image or enter a color value. The browser controls the system picker; a normal web page cannot silently sample another app.
3. Edit the gradient intentionally. In the animated text tool, arrange gradient stops and adjust their positions. Stop color controls the hue; position controls where it falls along the blend. Moving two stops close together creates a faster transition. Keep a copy of the gradient configuration for later edits.
4. Check the final use. Review the palette on light and dark backgrounds and at the intended text size. Check readability separately from whether the colors look attractive. A preview canvas, transparent export and final website background can produce different perceived results.

Worked Example

A blue-to-orange gradient with stops at 0% and 100% spreads the transition across the full range. Moving the orange stop to 40% reaches orange earlier; it does not simply rotate the gradient. Angle is a separate control.

Before You Finish

• Test text legibility over every part of a changing gradient.
• Keep shadows and glow off unless they improve the final design.
• Export editable gradient information as well as the generated code.

Limits and Privacy

Automatic palette extraction groups pixel colors; it cannot know which color is your official brand primary. Display calibration, browser support and compression affect what you see.

Image sampling and gradient editing happen locally. Screen picking returns the chosen color through the browser’s supported picker, not a continuous desktop capture.

Make a Short Video or GIF That Actually Plays Well

Choose the format and scale for the destination before spending time on a large conversion.

1. Trim before rendering. Identify the shortest useful clip. A few seconds of a focused action is often easier to understand than a long loop. Keep the source recording so you can revise the selection without recompressing an export.
2. Choose motion and size together. Frame rate affects motion smoothness and the number of frames that must be processed. Resolution affects the size of every frame. Start with modest settings, then increase only where the difference is visible at the final display size.
3. Check loop boundaries. Compare the last and first frames. A sudden camera position change is visible every time a GIF repeats. Try a shorter selection or an intentional back-and-forth sequence when that fits the action. Avoid fast flashing effects.
4. Inspect the actual export. Play the downloaded file in another viewer and at the destination. A preview is not proof that a completed render has the expected duration, orientation, dimensions or audio. GIF has no audio; use video when sound matters.

Worked Example

A 4-second animation at 12 frames per second contains about 48 frames. Doubling both width and height creates four times as many pixels per frame, before also considering frame-rate changes.

Before You Finish

• Inspect small lettering and gradients for palette artifacts.
• Confirm that the chosen destination accepts the file type and dimensions.
• Test a short clip before processing a large batch; memory limits vary by device.

Limits and Privacy

Local media processing depends on codecs, browser capability and available memory. GIF uses a limited palette and can be larger than a comparable video. A frame extractor is not a full editing timeline.

Local conversions run on this device. Optional engine downloads may need a connection, but importing a source file is not the same as uploading it to a remote encoder.

Build a Personal Toolbox and Back It Up

Use favorites, pinned working tools and Data Passport for different jobs rather than relying on browser storage alone.

1. Save useful destinations. Favorites are a quick way to remember tools. Use the heart in the main menu to return to the Favorites page. Recently Used is a browsing convenience, not a durable project archive.
2. Pin tools you work in repeatedly. On Pinned Tools, search and select a result to add the actual working tool. Workspaces load as you scroll to them. Collapse an interface to reduce clutter without unmounting its current state. The clickable tool name opens the full page and its instructions.
3. Use the correct backup. Export Pins saves the collection of tool links, not every tool’s working data. A tool’s own JSON export is usually the best editable backup for a project. Favorites export/import handles favorite selections. Data Passport covers supported settings and saves, not every in-memory form or open file.
4. Test recovery before you need it. Import a backup in another browser profile, confirm the expected settings or project entries, and open representative tools. Keep the original backup until you know the transfer worked. Treat any shareable passport link or QR code containing personal data as private.

Worked Example

Pinning Show Rundown makes the editor easy to reach, but exporting only the pins list does not back up the rundown rows. Export the rundown spreadsheet too. Likewise, save a character JSON file rather than relying only on a PDF printout.

Before You Finish

• Save or export before unpinning, changing views or leaving a page with unsaved work.
• Keep backups somewhere other than the browser that holds the original.
• Review what a passport contains before sending its link or QR code to another person.

Limits and Privacy

Browser storage can be cleared, blocked or limited. Pinned interfaces may use substantial memory when many are open; collapse unused tools and keep backups. Some tool state is intentionally temporary and is not part of Data Passport.

Favorites and pins are personal browser data, not public Featured Tools. Owner-published Featured Tools and category defaults do not expose visitor saves.