Yolosoft Company Logo
← Back to products
Web Toolbox

Yolosoft Packly

Asset Minifier Image Tools API-ready

A lightweight web toolbox designed for fast iteration, consistent output, and safer sharing. Packly includes Asset Minifier (CSS & JS), Ignore File Generator, Blur Face, Crop Image, and Resize Image. Use it in the browser for quick fixes, or integrate public APIs into scripts and pipelines for repeatable transformations.

Open Packly Open Minifier Open Ignore Generator Open Blur Face Open Crop Image Open Resize Image
On this page
What is Packly? Design principles Asset Minifier Ignore File Generator Blur Face Crop Image Resize Image Automation Roadmap FAQ
Utility today
Minifier + Ignore + Blur + Crop + Resize
Languages
CSS + JS
Output formats
code + images + metadata options
Docs
quick-start included
Quick facts

Packly summary

Category
Lightweight web toolbox
Utility today
Minifier + Ignore + Blur + Crop + Resize
Automation
Public JSON API
Next steps

Start in the UI to find the right settings, then move the same configuration into automation.

Open Packly Open Ignore Generator Open Blur Face Open Crop Image Open Resize Image Open API docs View all products
Popular searches

web toolbox · CSS minifier · JavaScript minifier · ignore file generator · blur faces in images · privacy image anonymization · crop image online · resize image online · image output presets · automation APIs

What is Packly?

Packly is Yolosoft’s lightweight web toolbox for practical, repeatable workflows. Instead of a single all-in-one platform, it focuses on focused browser tools you reach for every week: minifying assets, generating ignore files, anonymizing images, cropping visuals, and resizing outputs for web, social, and docs.

The goal is simple: help teams standardize small tasks so releases stay quick, consistent, and easy to repeat — in the browser and in CI/CD.

For developers

Paste, optimize, and copy output in seconds while you’re in the middle of a task — no setup, minimal clicks, and predictable results.

For teams

Standardize small build steps so output stays consistent across projects, environments, and contributors.

For pipelines

Use public JSON endpoints to automate repetitive transformations in CI/CD and keep releases fast and repeatable.

Design principles

Packly utilities are built around fast UI workflows, clear documentation, and automation-friendly integrations — without adding ceremony.

UI-first

Instant results without refresh (AJAX) so you can iterate quickly while debugging or preparing a release.

API-ready

Public endpoints make automation simple when a utility supports it — integrate from scripts and CI/CD.

Predictable responses

Consistent JSON envelopes help tooling parse results and handle errors reliably.

Defensive limits

Validated payloads and size constraints protect the system and keep behavior consistent.

Responsive + animated

Mobile-friendly UX using scroll reveal patterns so information stays readable on every device.

Current utility: Asset Minifier (CSS + JS)

Minify CSS and JavaScript from one interface. Copy minified output, download .min files, or export a ZIP for sharing and releases.

UI workflow

  1. Open the Minifier UI at /minifier.
  2. Paste CSS or JS and adjust settings if needed.
  3. Click Minify (AJAX) to get results without page refresh.
  4. Copy output, download a .min file, or export a ZIP bundle.

What you can automate

  • Send minify requests via the public JSON API.
  • Download ZIP bundles for release artifacts.
  • Keep transformations stable across branches and environments.

Minifier API docs

Exact endpoint routes, request models, and error-handling are documented at /minifier/docs. Start in the UI to validate settings, then move the same configuration into automation.

New utility: Ignore File Generator (.gitignore + .dockerignore)

Ignore files are small text files with a big impact: they tell Git and Docker which files should not be committed or shipped to a build context. The result is cleaner diffs, faster reviews, fewer “works on my machine” artifacts, and smaller Docker builds.

With Packly Ignore File Generator you pick the type (.gitignore or .dockerignore), search a curated template for your stack (for example .NET, Node.js, Python, Java, Go), and download a ready-to-use ignore file in seconds. You can then commit it to your repo and adjust rules as your project evolves.

Templates
9 curated templates
Picker
Searchable selector
Output
.gitignore / .dockerignore
Works with
Any Git repo + Docker builds

How it works

  1. Select the type (Git or Docker) and search by language, framework, or tool (for example .NET, Node.js, Python).
  2. Choose the closest match for your stack from a curated template list.
  3. Click Generate to download a plain-text file named .gitignore or .dockerignore.
  4. Place it in the correct location, commit it, and revisit rules when your tooling changes.

Why ignore files matter

A good ignore file improves repository hygiene: it reduces noise in pull requests, prevents accidental commits, and keeps Docker builds focused on what actually matters.

Cleaner commits

Ignore build outputs, caches, and generated files so pull requests focus on meaningful source changes — not churn from your toolchain.

Fewer merge conflicts

Avoid committing machine-specific folders and IDE artifacts that differ across developers, OSes, and CI runners.

Safer repositories

Reduce the risk of leaks by ignoring common environment files and local-only configs (for example .env files or local settings) that may contain secrets.

Faster setup

Start from a curated baseline for your stack, then fine-tune as your project grows — without reinventing ignore patterns every time.

Best practices and practical tips

  • Ignore build outputs and cache folders early (bin/, obj/, dist/, node_modules/) before they show up in commits.
  • Do not ignore source files required to build from scratch (for example migrations or generated code that is part of your release process).
  • Ignore local environment files that can contain secrets (.env, local settings) and prefer secret managers in CI/CD.
  • Use comments to document why a rule exists so future contributors understand the intent.
  • Review ignore rules when you add new tooling, switch frameworks, or introduce a new build step — especially for Docker builds.

Small example

Example rules you can adapt for many projects:

# Build outputs
bin/
obj/
dist/

# Logs
*.log

# Environment
.env

Utility highlight: Blur Face

Blur Face helps teams anonymize screenshots and photos before sharing externally. It supports one or many input images, auto and manual detection modes, and multiple blur styles for practical privacy workflows.

Blur Face workflow

  1. Upload one or multiple images in the browser.
  2. Choose auto detection for speed or manual mode for targeted control.
  3. Adjust blur style, blur strength, and optional portrait matching settings.
  4. Download single-image output or ZIP results for multi-image batches.

Privacy and sharing notes

  • Review output before publishing and re-run in manual mode if needed.
  • Use strong enough blur settings for your legal/compliance context.
  • Consider metadata hygiene when sharing anonymized images externally.

Utility highlight: Crop Image

Crop Image provides precision controls for production-ready image exports. Teams can define coordinates and dimensions, manage output formats and quality, and generate multiple output sizes from one crop intent.

Key capabilities

  • Two-way sync between visual crop box and numeric controls.
  • Preset save/load for repeatable workflows.
  • Multiple output sizes including original, web, retina, and custom.
  • Format, quality, DPI, transparency/fill, and filename template options.

Typical usage flow

  1. Select one image and compose the crop area visually.
  2. Fine-tune width, height, x, y, rotation, and aspect ratio.
  3. Choose output format and quality profile for target channels.
  4. Export with deterministic filenames for easier automation and publishing.

Utility highlight: Resize Image

Resize Image helps teams standardize image dimensions for web pages, social media, docs, and marketplaces. It supports batch uploads, advanced fit modes, output format/quality control, and naming patterns for repeatable exports.

Key capabilities

  • Resize by percentage or exact pixel targets with optional aspect-ratio lock.
  • Fit modes for contain, cover, stretch, pad, and crop scenarios.
  • Output controls for format, quality, resampling, metadata preservation, and transparent padding.
  • Deterministic naming with suffix or custom placeholders for pipeline-friendly exports.

Typical usage flow

  1. Upload one or many images and switch previews through thumbnails.
  2. Select resize mode (percentage or pixels), then configure fit mode and anti-enlarge behavior.
  3. Choose output format, quality, and metadata options to match your channel requirements.
  4. Resize and download single output or ZIP batches with stable naming patterns.

Automation-ready APIs

Packly is designed for both quick, interactive use and repeatable automation. Many teams start in the UI, then move stable transformations into pipelines once settings are proven.

1) Explore in the browser

Paste an input, tune settings, and preview output instantly. Ideal for one-off tasks and debugging.

2) Standardize settings

Once a configuration is validated, keep it consistent across projects so output stays predictable.

3) Automate with the public API

Use Packly’s endpoints from scripts or CI/CD to keep releases fast and repeatable.

Where Packly fits best

  • Front-end asset pipelines: minify generated CSS/JS artifacts before publishing.
  • Internal tooling: build helpers on top of a stable API surface.
  • Release preparation: generate final .min outputs and export ZIPs for distribution.
  • Developer productivity: quick results, minimal clicks, responsive layout.

Roadmap: a growing set of utilities

Packly currently includes Minifier, Ignore File Generator, Blur Face, Crop Image, and Resize Image, and the site structure is prepared for additional utilities. New tools can add their own SEO sections on dedicated pages and the homepage can feature them as they ship.

Potential utilities (examples)

  • JSON formatter / validator
  • HTML formatter / minifier
  • URL encode / decode
  • Base64 encode / decode
  • Hash helpers (e.g., SHA-256)
  • Case converters, regex helpers, and text cleanup utilities

What stays consistent as Packly grows

  • Responsive UI with copy-first output
  • AJAX interactions where page refresh isn’t needed
  • Public API endpoints for automation (when applicable)
  • Clear docs with examples and defensive limits

Homepage FAQ

Packly is a lightweight web toolbox for common build and privacy tasks. It works for quick browser usage and for automation via public APIs.

Packly currently includes Asset Minifier (CSS + JS), Ignore File Generator, Blur Face, Crop Image, and Resize Image. Minifier docs are available at /minifier/docs.

Each utility that supports automation includes dedicated docs. For the Minifier, start with /minifier/docs.

Yes. Validate output in the UI first, then use the same settings via the public API from scripts or CI/CD pipelines.

Yes. Packly is designed as a suite of small tools, so new utilities can be added over time while UI and API patterns remain consistent.

Packly is designed for request/response processing. Treat inputs as sensitive and ensure your deployment’s logging and monitoring policies align with your security requirements.

No. The generator is designed to be safe by default: you do not paste source code, and the server only needs a template id and type to return an ignore file. The response is a plain-text download intended to be reviewed and committed by you.

Place .gitignore at your repository root and commit it. Place .dockerignore next to your Dockerfile (or wherever your build context starts) to avoid sending unnecessary files to Docker.