Build a Standalone Media Converter .EXE with AutoHotkey v2 GUI
Experienced developers can quickly build a self-contained Windows .EXE (Windows 7–11) without external dependencies. Leveraging AutoHotkey v2 and AI tools, this solution enables recursive processing of photos and videos via ffmpeg and ImageMagick. The entire codebase is under 1,500 lines, resulting in a compact 500 KB binary. The logic mirrors a command-line script: downloading packages via winget, re-encoding media into modern codecs (HEVC, AVC, JPEG) with GPU acceleration.
Setup: Research & Tech Stack Selection
During research, outdated tools lacking HEIC/HEIF and WEBM support were identified. For research, Perplexity is recommended—it aggregates data cleanly, without ads or links.
Task: Batch process archives from AI-generated content (source files 7–10 MB, compressed to 2 MB without quality loss). Recursive folder traversal with support for mixed formats from cameras and smartphones.
AI suggests AutoHotkey v2 as the optimal stack: minimal dependencies, native .EXE compilation, built-in GUI capabilities. Alternatives include AutoIt and PureBasic.
Requirements Specification
Describe your task to the AI via voice or text: 'Minimalist GUI for Windows 7–11. Recursively scans folders, uses ffmpeg/ImageMagick for media compression. No C++ or .NET frameworks.' Receive clarifying questions and a final spec.
System prompt for stable output:
When I write code, always display it in a code block. When editing: 'Iteration N. Description'. Increment version in code (e.g., v2.2). Provide full code when changes exceed one line. Small edits go separately.
Do not use bold/italic/emoticons unless specified.This prevents hallucinations after 10–15 iterations (up to 1,000 lines).
MVP Development
Start a new dialogue with the spec and tech stack. Assign 3–5 tasks at a time: folder traversal logic, ffmpeg calls, progress bar.
- Install dependencies (winget install ffmpeg imagemagick).
- Recursive folder scanning (supports subfolders).
- Compression settings: JPEG/AVC/HEVC, GPU options.
- Progress logging.
- Error handling (unsupported formats).
The MVP can be ready by evening. Then focus on GUI refinements.
GUI: From Prototype to Release
Generate mockups in Gemini or Nano Banana: 'GUI like Nero Burning ROM from the 2000s—retro style with buttons, sliders'.
AutoHotkey v2 tricks:
- Color zones instead of system buttons (click handling).
- Custom sliders built on modal windows.
- Menus and progress bars using native controls.
Use Dribbble/Freepik references in prompts. For fine-tuning, Photoshop beats chat interfaces (positioning, spacing).
Iterations:
- Iteration 1–5: basic layout.
- 6–10: styling (VB6 nostalgia vibe).
- 11+: small features (menu symmetry).
Debugging & Optimization
Test option combinations manually: compression checkboxes, paths, formats. Automated testing via chat is inefficient (×3–5 slower).
Common bugs:
- Symbolic link traversal issues.
- GPU access during background operations.
- Memory leaks with large archives (>100 GB).
Optimizations:
- Asynchronous progress updates.
- Pause/resume functionality.
- Log output saved to file.
The third evening is reserved for edge cases.
Key Takeaways
- AutoHotkey v2 compiles directly to .EXE without runtime (just 500 KB).
- Recursive processing: photos (HEIC → JPEG), videos (WEBM → HEVC).
- GPU compression reduces archive sizes by ×3–5.
- 10–15 AI iterations before degradation.
- Native GUI elements only—no libraries, compatible with Windows 7+.
— Editorial Team
No comments yet.