TOOLDAM GUIDE

A practical guide to working with files

Learn how to handle images, PDFs and data files with more confidence. Find clear guidance on formats, quality, file size and common conversion issues.

01

JPG, PNG or WebP: which image format should you choose?

Photos, screenshots, logos and transparent graphics have different needs, so the best format depends on the image.

02

Image compression and quality: how far can you go?

Compression reduces file size, but it can also affect texture, text and gradients. The safe level depends on the image and its final display size.

03

If you halve image resolution, does file size halve too?

Reducing width and height cuts the pixel count much faster, but the final file size still depends on image content and compression.

04

How large should images for a website be?

Web images should balance actual display size, screen density and transfer size so they stay sharp without unnecessary downloads.

05

Why is a PDF so large? Check the cause before compressing

PDF size can be driven more by embedded images, fonts, graphics and existing compression than by the number of pages.

06

What changes when you compress a PDF?

Compression results depend on what the document contains. Image-heavy PDFs especially need checks for text sharpness and photo quality.

07

JPG or PNG when converting PDF pages to images?

Pages dominated by photos and pages full of small text or lines can show very different size and sharpness results in JPG and PNG.

08

What to check before merging several PDFs

When PDFs come from different sources, check more than page order: orientation, page size, blank pages and duplicates can all affect the final document.

09

JSON vs CSV: which should you use when moving data?

CSV fits rows and columns; JSON can represent nested arrays and objects. The right choice depends on the structure you need to preserve.

10

Why Korean text can break in CSV files

If the program that creates a CSV and the program that opens it assume different character encodings, Korean text can appear corrupted. UTF-8 and BOM handling are common checkpoints.