Local-first image workbench
tobeimage turns compression, conversion, crop, resize, watermarking, and image-to-PDF export into a shorter browser-based path for publishing, submission, and archive prep.
Built for frequent image tasks before publishing, submission, and archive prep, helping you decide whether to compress, crop, resize, or normalize format first.
Define the problem first, enter the first step second, and end with a file that is easier to publish, submit, or archive.
Best for
Not built for
Local-first
It fits publishing prep, form submission, archive packaging, and everyday asset cleanup without sending people into a heavier back office first.
The homepage is optimized for frequent, fast, outcome-driven image work.
Task-led
Choosing the problem type before the feature page usually leads to fewer do-overs than guessing from tool names.
Defining the problem first usually gets you to a usable result faster.
Delivery-ready
Compression, crop, resize, format cleanup, and PDF export are treated as connected steps instead of isolated edits.
Once the final delivery goal is clear, the first step becomes much easier to choose.
Turn common tasks into a steadier sequence, reduce do-overs, and get to a usable result more reliably.
Publishing flow
A practical order for avatars, covers, product heroes, and social graphics that need both framing and spec control.
Set framing first, match platform specs second, and reduce file weight last so the final asset stays publication-ready.
Submission flow
A strong fit for scans, contract attachments, form images, and mixed materials that should end as one file.
Clean up mixed-source files first, then confirm page order and layout before exporting the submission-ready PDF.
If you want fewer do-overs, start with these distinctions.
Weight vs Specs
Decide first whether the blocker is file weight or dimensions.
Use Compression
Best for email attachments, forms, web media, and any publishing flow where lighter files matter.
Open CompressionUse Resize
Best for ad-slot specs, social cover sizes, and layout-driven dimensions without changing framing.
Open ResizeConclusion: use compression for weight, resize for specs.
Framing vs Specs
Decide whether the problem is in the frame or only in the output specs.
Use Crop
Use it for avatars, covers, product heroes, and any image that needs reframing.
Open CropUse Resize
Once the frame is correct and only target specs remain, resizing is the better tool.
Open ResizeConclusion: for avatars and covers, crop first and resize after.
Format choice
Format choice usually depends on compatibility, transparency, and web delivery, not just novelty.
Transparency first
If an asset depends on transparency, converting it to JPG too early removes a useful editing property.
If you already know what needs to be done, open the matching feature and finish the task faster.
These questions cover the decisions people most often get stuck on when they first arrive here.
Start by defining what “too large” means. If the blocker is file weight or upload rejection, start with Image Compression. If the issue is pixel dimensions, start with Image Resize.
Because these tasks usually fail on framing, ratio, and whitespace before they fail on exact dimensions. Start with Image Crop, then move to Image Resizeonce the frame is correct.
JPG is best for compatibility-first delivery and photo assets, PNG fits transparency and editable design assets, and WebP is usually better for browser delivery. If you are still unsure, start in the Image Conversion Workbench.
Use the workbenchwhen sources are mixed or the target is still undecided. If you already know the output, a fixed target pagewill be shorter.
Keep image files when they still need upload, sharing, or separate processing. Turn them into PDFwhen the goal is submission, archive, or printing.